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
You can get the online documentation with ``bzr help revisionspec``.
10
Revision specs and ranges
11
=========================
13
``bzr`` has a very expressive way to specify a revision, or a range of revisions.
14
We'll take the example of the ``log`` command.
16
To specify a range of revisions, use for example::
20
You can omit one bound like::
26
Omitting the lower bound doesn't work on versions of ``bzr`` prior to 0.14.
28
Other commands, like ``bzr cat`` take only one revision, not a range, like::
32
Available revision specs
33
========================
35
The revision, or the bounds of the range, can be one of
37
+----------------------+------------------------------------+
38
| argument type | description |
39
+----------------------+------------------------------------+
40
| *number* | revision number |
41
+----------------------+------------------------------------+
42
| **revno**:*number* | positive revision number |
43
+----------------------+------------------------------------+
44
| **last**:*number* | negative revision number |
45
+----------------------+------------------------------------+
46
| **revid**:*guid* | globally unique revision id |
47
+----------------------+------------------------------------+
48
| **before**:*rev* | leftmost parent of ''rev'' |
49
+----------------------+------------------------------------+
50
| **date**:*value* | first entry after a given date |
51
+----------------------+------------------------------------+
52
| **ancestor**:*path* | last merged revision from a branch |
53
+----------------------+------------------------------------+
54
| **branch**:*path* | latest revision on another branch |
55
+----------------------+------------------------------------+
60
Positive numbers denote revision numbers in the current branch. Revision
61
numbers are labelled as "revno" in the output of ``bzr log``. To display
62
the log for the first ten revisions::
66
Negative numbers count from the latest revision, -1 is the last committed
69
To display the log for the last ten revisions::
77
The same as *number*, except that negative numbers are not allowed.
80
The same as -''number''. **last:1** means the last commited revision.
85
**revid** allows specifying a an internal revision ID, as shown by ``bzr
86
log`` and some other commands.
90
$ bzr log -r revid:Matthieu.Moy@imag.fr-20051026185030-93c7cad63ee570df
97
''rev'' specifies the leftmost parent of ''rev'', that is the revision
98
that appears before ''rev'' in the revision history, or the revision that
99
was current when ''rev'' what comitted.
101
''rev'' can be any revision specifier and may be chained.
105
$ bzr log -r before:before:4
114
''value'' matches the first history entry after a given date, either at
115
midnight or at a specified time.
122
* A **YYYY-MM-DD** format date.
123
* A **YYYY-MM-DD,HH:MM:SS** format date/time, seconds are optional (note the
126
The proper way of saying "give me all the log entries for today" is::
128
$ bzr log -r date:yesterday..date:today
134
specifies the common ancestor between the current branch and a
135
different branch. This is the same ancestor that would be used for
138
*path* may be the URL of a remote branch, or the file path to a local branch.
140
For example, to see what changes were made on a branch since it was forked
143
$ bzr diff -r ancestor:../parent
149
``path`` specifies the latest revision in another branch.
151
``path`` may be the URL of a remote branch, or the file path to a local branch.
153
For example, to get the differences between this and another branch::
155
$ bzr diff -r branch:http://example.com/bzr/foo.dev
added
removed
doc/specifying_revisions.txt
