crew repo and bookmarks

Matt Mackall mpm at selenic.com
Wed Jun 20 16:50:03 CDT 2012


On Wed, 2012-06-20 at 22:40 +0200, Patrick Mézard wrote:
> Le 07/06/12 18:41, Bryan O'Sullivan a écrit :
> > On Wed, Jun 6, 2012 at 11:27 PM, Patrick Mézard <patrick at mezard.eu> wrote:
> > 
> >>
> >> What will it bring to the default/stable named branches scheme?
> > 
> > 
> > Nothing in particular. My main concern here is to ensure that core
> > developers are forced to actually use bookmarks, even if only implicitly.
> > The fact that they are an attractive feature, but one that Mercurial's own
> > developers generally don't use, is a worrisome combination.
> 
> So? :-)

In favor. But that's not news: I proposed this quite a while ago.

> I have started to test a combination of obsolete/evolve + bookmarks
> for feature branches on mercurial. Being completely new to bookmarks,
> what I missed most compared to an mq/qqueue setup is to easily update
> back to main stable/default heads. Augie remotebranches extension
> solves this nicely but I am curious how regular bookmarks would fare.
> That said I am little skeptical about Thomas proposal to create
> stable/default bookmarks as we discourage naming bookmarks like
> existing named branches.

Well, _obviously_ the names should be crew and crew-stable.

-- 
Mathematics is the supreme nostalgia of our time.




More information about the Mercurial-devel mailing list