Git workflow in Mercurial

[Peter Arrenbrecht]

On Fri, Dec 12, 2008 at 7:50 PM, Leslie P. Polzer
<sky at viridian-project.de> wrote:
>
> Hi once more,
>
> a fellow developer proposed this to me:
>
>> [...] small topic branches. Those are easy to merge, easy to
>> port and easy to separate out, e.g. you can easily point to a bunch of
>> changesets and say "get these to get the new navigation" or something.
>
>> git lets you do that easily, plus it lets you actually share these
>> topic branches between people. You can say "I want to pull changes from
>> Leslie's topic branch X into my local branch Y", which is very useful,
>> plus it lets me keep all these in a single tree in a single
>> directory. There might be a way to do that with hg (named branches), but
>> I think it isn't as smooth as the git way.
>
> How would we approach this best with hg? Named branches, local branches,
> pbranch?

If the changes done in the topic branches are meant to be submitted
upstream as patches (via email, or whatever) and one branch tracks the
evolution of one such patch, then pbranch is a good fit. Otherwise,
stay away from it. It would only add unnecessary overhead.
-parren