branches & 'hg update'

[Matt Mackall]

On Thu, 2009-06-18 at 12:19 +0200, Aurélien Campéas wrote:
> On Thu, Jun 18, 2009 at 04:57:15AM -0500, Matt Mackall wrote:
> > On Thu, 2009-06-18 at 11:46 +0200, Aurélien Campéas wrote:
> > > Hello,
> > > 
> > > Using mercurial 1.2.1 (the debian packaged version), I note that :
> > > 
> > > hg branch 9.5
> > > 
> > > [ add, commit ]
> > > 
> > > creates a 9.5 branch and allows doing stuff within
> > > 
> > > but then, from, say, default :
> > > 
> > > hg up 9.5
> > > 
> > > (or '9.5') does not drive me back to that branch ...
> > > 
> > > It works perfectly with a non-dotted branch name (9_5).
> > > 
> > > Is this a known bug ? (skimming over
> > > http://www.selenic.com/mercurial/bts/) I'd say no, but ...
> > 
> > Do you have a tag named 9.5?
> > 
> 
> I had created a 9.5 tag inside the branch (to make it a living branch)
> indeed.

> I don't see anything related to tags in the 'update' docmumentation
> (but then, I've been known to not see bug things sitting in front of
> me ...). Even the part about branches is a bit terse:
> 
> hg update [-C] [-d DATE] [[-r] REV]

See 'hg help revisions'. Just about any place where we take a revision,
we can take:

- a revision number
- a changeset identifier or prefix
- a tag
- a branch name
- a bookmark
- one of the special identifiers '.', tip, or null

Making new identifiers that conflict with each other will make your life
interesting.

-- 
http://selenic.com : development and support for Mercurial and Linux