effective use of in-repository branching
Matt Mackall
mpm at selenic.com
Wed Feb 7 23:44:31 UTC 2007
On Wed, Feb 07, 2007 at 06:48:09PM -0500, Jesse Keating wrote:
> On Wednesday 07 February 2007 16:06, Matt Mackall wrote:
> > We currently don't have any mechanism for transmitting info that's not
> > "checked in". And I'd like to avoid adding one, as it would mean
> > having to re-solve a large set of problems. So the .hg/hgrc thing
> > doesn't really work.
> >
> > I also don't really like the idea of having a hard-coded name like "HEAD"
> > or "default" that's the default for clone operations.
> >
> > One possibility would be to piggyback on the tags capability: to set
> > the name of the default branch, you tag a revision in that branch
> > "default-branch". But that's really ugly.
> >
> > So we may just want to do the fixed name thing. If there's a branch
> > marked "default" (or whatever name), we use it. Otherwise, use tip.
>
> Why can't the 'default' branch be the unnamed branch, or a branch of name ''.
> That way named branches have to be explicitly accessed by name, otherwise you
> just get ''.
It's a possibility. One current problem here is that the branch cache
currently ignores ''. But I believe Thomas has a fix for that.
--
Mathematics is the supreme nostalgia of our time.
More information about the Mercurial
mailing list