Mercurial Workflow: Feature seperation via named branches

Martin Geisler mg at aragost.com
Fri Jun 17 04:44:56 CDT 2011


Pierre-Yves David <pierre-yves.david at logilab.fr> writes:

> On Thu, Jun 16, 2011 at 04:57:29PM +0200, Martin Geisler wrote:
>
>> >> By the way, maybe we should begin using some bookmarks in Mercurial
>> >> itself: Henrik and I could push the patches for abandoned changesets
>> >> as a branch with a bookmark and you and others could give much better
>> >> and faster feedback in the form of commits instead of just chatting
>> >> here.
>> >
>> > Hmmm, that'll change everyone's workflow against crew. I'd rather do
>> > this experiment in another repo.
>> 
>> I agree with you -- the crew repository is not the best place to start
>> this experiment.
>> 
>> We could start it outside of crew if we agree that it is okay to
>> pull+merge the resulting repository back into crew at some point instead
>> of rebasing the changesets.
>
> I don't see pull+merge he resulting repository in crew as a good idea.

Because you would rather that we keep working with patches of patches (a
versioned MQ)? or some other reason?

-- 
Martin Geisler

aragost Trifork
Professional Mercurial support
http://mercurial.aragost.com/kick-start/


More information about the Mercurial mailing list