Mercurial > public > mercurial-scm > hg
diff mercurial/help/revisions.txt @ 30771:c2cbc1b050db
help: explain that revsets can be used where 1 or 2 revs are wanted
We did not seem to document that one can do things like "hg up :@"
where the last revision of the revset ":@".
| author | Martin von Zweigbergk <martinvonz@google.com> |
|---|---|
| date | Wed, 11 Jan 2017 23:13:00 -0800 |
| parents | d0a758e7002b |
| children | 5dd67f0993ce |
line wrap: on
line diff
--- a/mercurial/help/revisions.txt Wed Jan 11 22:46:07 2017 -0800 +++ b/mercurial/help/revisions.txt Wed Jan 11 23:13:00 2017 -0800 @@ -29,6 +29,12 @@ uncommitted merge is in progress, "." is the revision of the first parent. +Finally, commands that expect a single revision (like ``hg update``) also +accept revsets (see below for details). When given a revset, they use the +last revision of the revset. A few commands accept two single revisions +(like ``hg diff``). When given a revset, they use the first and the last +revisions of the revset. + Specifying multiple revisions ============================= @@ -188,3 +194,13 @@ release:: hg log -r "(keyword(bug) or keyword(issue)) and not ancestors(tag())" + +- Update to commit that bookmark @ is pointing too, without activating the + bookmark (this works because the last revision of the revset is used):: + + hg update :@ + +- Show diff between tags 1.3 and 1.5 (this works because the first and the + last revisions of the revset are used):: + + hg diff -r 1.3::1.5