1
=============================
2
Specifying revision in Bazaar
3
=============================
5
Description of the subarguments for ``-r`` as used by commands such as
6
**bzr log** and **bzr merge**.
8
Revision specs and ranges
9
=========================
11
**bzr** has a very expressive way to specify a revision, or a range of revisions.
12
We'll take the example of the **log** command.
14
To specify a range of revisions, use for example::
18
You can omit one bound like::
24
Omitting the lower bound doesn't work on currently released versions.
26
Other commands, like **bzr cat** take only one revision, not a range, like::
30
Available revision specs
31
========================
33
The revision, or the bounds of the range, can be one of
35
+----------------------+------------------------------------+
36
| argument type | description |
37
+----------------------+------------------------------------+
38
| *number* | revision number |
39
+----------------------+------------------------------------+
40
| **revno**:*number* | positive revision number |
41
+----------------------+------------------------------------+
42
| **last**:*number* | negative revision number |
43
+----------------------+------------------------------------+
44
| **revid**:*guid* | globally unique revision id |
45
+----------------------+------------------------------------+
46
| **before**:*rev* | leftmost parent of ''rev'' |
47
+----------------------+------------------------------------+
48
| **date**:*value* | first entry after a given date |
49
+----------------------+------------------------------------+
50
| **ancestor**:*path* | last merged revision from a branch |
51
+----------------------+------------------------------------+
52
| **branch**:*path* | latest revision on another branch |
53
+----------------------+------------------------------------+
58
Positive numbers denote revision numbers in the current branch. Revision
59
numbers are labelled as "revno" in the output of **bzr log**. To display
60
the log for the first ten revisions::
64
Negative numbers count from the latest revision, -1 is the last committed
67
To display the log for the last ten revisions::
75
The same as *number*, except that negative numbers are not allowed.
78
The same as -''number''. **last:1** means the last commited revision.
83
**revid** allows specifying a an internal revision ID, as show by **bzr
84
testament** and some other commands.
88
$ bzr log -r revid:Matthieu.Moy@imag.fr-20051026185030-93c7cad63ee570df
95
''rev'' specifies the leftmost parent of ''rev'', that is the revision
96
that appears before ''rev'' in the revision history, or the revision that
97
was current when ''rev'' what comitted.
99
''rev'' can be any revision specifier.
103
$ bzr log -r before:before:4
112
''value'' matches the first history entry after a given date, either at
113
midnight or at a specified time.
120
* A **YYYY-MM-DD** format date.
121
* A **YYYY-MM-DD,HH:MM:SS** format date/time, seconds are optional (note the
124
The proper way of saying "give me all the log entries for today" is::
126
$ bzr log -r date:yesterday..date:today
132
specifies the common ancestor between the current branch,and a
133
different branch. This is the same ancestor that would be used for
136
*path* may be the URL of a remote branch, or the file path to a local branch.
138
For example, to see what changes were made on a branch since it was forked
141
$ bzr diff -r ancestor:../parent
147
''path'' specifies the latest revision in another branch.
149
''path'' may be the URL of a remote branch, or the file path to a local branch.
151
For example, to get the differences between this and another branch::
153
$ bzr diff -r branch:http://example.com/bzr/foo.dev
added
removed
doc/specifying_revisions.txt
