[Bug 3720] New: The order of precedence for revision specification should be documented

[bugzilla-daemon at bz.selenic.com]

http://bz.selenic.com/show_bug.cgi?id=3720

          Priority: normal
            Bug ID: 3720
                CC: mercurial-devel at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: The order of precedence for revision specification
                    should be documented
          Severity: bug
    Classification: Unclassified
                OS: All
          Reporter: alastair at alastairs-place.net
          Hardware: All
            Status: UNCONFIRMED
           Version: 2.4
         Component: Mercurial
           Product: Mercurial

It isn't clear whether e.g.

  hg update -r cafe

should update to a bookmark called "cafe", a tag called "cafe" or a revision
whose node ID starts with "cafe".  "hg help revs" doesn't really clarify what
order Mercurial checks for things, and while most cases can be clarified using
the revset notation, e.g.

  hg update -r tag(cafe)

this *doesn't work* for bookmarks because update doesn't realise that

  hg update -r bookmark(cafe)

is trying to do a bookmark update.

-- 
You are receiving this mail because:
You are on the CC list for the bug.