1
Revision specs and ranges
2
=========================
4
**bzr** has a very expressive way to specify a revision, or a range of revisions.
5
We'll take the example of the **log** command.
7
To specify a range of revisions, use for example::
11
You can omit one bound like::
17
Omitting the lower bound doesn't work on currently released versions.
19
Other commands, like **bzr cat** take only one revision, not a range, like::
23
Available revision specs
24
========================
26
The revision, or the bounds of the range, can be one of
28
+----------------------+------------------------------------+
29
| argument type | description |
30
+----------------------+------------------------------------+
31
| *number* | revision number |
32
+----------------------+------------------------------------+
33
| **revno**:*number* | positive revision number |
34
+----------------------+------------------------------------+
35
| **last**:*number* | negative revision number |
36
+----------------------+------------------------------------+
37
| **revid**:*guid* | globally unique revision id |
38
+----------------------+------------------------------------+
39
| **before**:*rev* | leftmost parent of ''rev'' |
40
+----------------------+------------------------------------+
41
| **date**:*value* | first entry after a given date |
42
+----------------------+------------------------------------+
43
| **ancestor**:*path* | last merged revision from a branch |
44
+----------------------+------------------------------------+
45
| **branch**:*path* | latest revision on another branch |
46
+----------------------+------------------------------------+
51
Positive numbers denote revision numbers in the current branch. Revision
52
numbers are labelled as "revno" in the output of **bzr log**. To display
53
the log for the first ten revisions::
57
Negative numbers count from the latest revision, -1 is the last committed
60
To display the log for the last ten revisions::
68
The same as *number*, except that negative numbers are not allowed.
71
The same as -''number''. **last:1** means the last commited revision.
76
**revid** allows specifying a an internal revision ID, as show by **bzr
77
testament** and some other commands.
81
$ bzr log -r revid:Matthieu.Moy@imag.fr-20051026185030-93c7cad63ee570df
88
''rev'' specifies the leftmost parent of ''rev'', that is the revision
89
that appears before ''rev'' in the revision history, or the revision that
90
was current when ''rev'' what comitted.
92
''rev'' can be any revision specifier.
96
$ bzr log -r before:before:4
105
''value'' matches the first history entry after a given date, either at
106
midnight or at a specified time.
113
* A **YYYY-MM-DD** format date.
114
* A **YYYY-MM-DD,HH:MM:SS** format date/time, seconds are optional (note the
117
The proper way of saying "give me all the log entries for today" is::
119
$ bzr log -r date:yesterday..date:today
125
specifies the common ancestor between the current branch,and a
126
different branch. This is the same ancestor that would be used for
129
*path* may be the URL of a remote branch, or the file path to a local branch.
131
For example, to see what changes were made on a branch since it was forked
134
$ bzr diff -r ancestor:../parent
140
''path'' specifies the latest revision in another branch.
142
''path'' may be the URL of a remote branch, or the file path to a local branch.
144
For example, to get the differences between this and another branch::
146
$ bzr diff -r branch:http://example.com/bzr/foo.dev
added
removed
doc/specifying_revisions.txt
