[chirp_devel] git vs hg patches [was: [PATCH 1/4] chirp.py: add --list-radios option (#2343)]
Zach Welch
Tue Feb 24 11:17:10 PST 2015
On 02/24/2015 10:51 AM, Dan Smith wrote:
...
>> I did a little web searching and reading after sending my last message,
>> and I wonder if that is true? hg-git provides the ability to pull from
>> and push to a remote git repository from within mercurial. Wouldn't
>> that be sufficient for interacting with gerrit?
>
> But they're not currently pushing, they're sending patches to the list,
> and mostly using mq for maintaining those patches on top of their repo
> (like quilt/guilt). In order to push from mercurial, you'd have to at
> least commit those patches and then you've got a more complicated
> problem for revising patches due to feedback, especially if tip is
> moving underneath.
Good points. Even with hg's mq, don't developers already need to handle
tip moving underneath? One of the reasons that I love git is 'rebase'
(and I see that mercurial has its own variant of it). These days, I
can't imagine doing development without it, particularly when dealing
with projects where the tip/master branch is moving fast.
> Regardless, I only think this is doable if all the major players are
> willing to move to git/gerrit. Lets give them time to respond (from
> their respective timezones).
Absolutely. I expect this issue to require ample discussion and
thorough consideration, so don't take my litany of questions as pressure
to do something right away.
--
Zach Welch
Mandolin Creek Farm
www.mandolincreekfarm.com
farm: 541-453-4131
cell: 541-740-3410
More information about the chirp_devel
mailing list