1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
|
Revision specs and ranges
=========================
**bzr** has a very expressive way to specify a revision, or a range of revisions.
We'll take the example of the **log** command.
To specify a range of revisions, use for example::
$ bzr log -r 1..4
You can omit one bound like::
$ bzr log -r 1..
$ bzr log -r ..4
Note::
Omitting the lower bound doesn't work on currently released versions.
Other commands, like **bzr cat** take only one revision, not a range, like::
$ bzr cat -r 42 foo.c
Available revision specs
========================
The revision, or the bounds of the range, can be one of
+----------------------+------------------------------------+
| argument type | description |
+----------------------+------------------------------------+
| *number* | revision number |
+----------------------+------------------------------------+
| **revno**:*number* | positive revision number |
+----------------------+------------------------------------+
| **last**:*number* | negative revision number |
+----------------------+------------------------------------+
| **revid**:*guid* | globally unique revision id |
+----------------------+------------------------------------+
| **before**:*rev* | leftmost parent of ''rev'' |
+----------------------+------------------------------------+
| **date**:*value* | first entry after a given date |
+----------------------+------------------------------------+
| **ancestor**:*path* | last merged revision from a branch |
+----------------------+------------------------------------+
| **branch**:*path* | latest revision on another branch |
+----------------------+------------------------------------+
Numbers
-------
Positive numbers denote revision numbers in the current branch. Revision
numbers are labelled as "revno" in the output of **bzr log**. To display
the log for the first ten revisions::
$ bzr log -r ..10
Negative numbers count from the latest revision, -1 is the last committed
revision.
To display the log for the last ten revisions::
$ bzr log -r -10..
revno, last
-----------
**revno**:*number*
The same as *number*, except that negative numbers are not allowed.
**last**:*number*
The same as -''number''. **last:1** means the last commited revision.
revid
-----
**revid** allows specifying a an internal revision ID, as show by **bzr
testament** and some other commands.
For example::
$ bzr log -r revid:Matthieu.Moy@imag.fr-20051026185030-93c7cad63ee570df
before
------
**before**
''rev'' specifies the leftmost parent of ''rev'', that is the revision
that appears before ''rev'' in the revision history, or the revision that
was current when ''rev'' what comitted.
''rev'' can be any revision specifier.
For example::
$ bzr log -r before:before:4
...
revno: 2
...
date
----
**date**
''value'' matches the first history entry after a given date, either at
midnight or at a specified time.
Legal values are:
* **yesterday**
* **today**
* **tomorrow**
* A **YYYY-MM-DD** format date.
* A **YYYY-MM-DD,HH:MM:SS** format date/time, seconds are optional (note the
comma)
The proper way of saying "give me all the log entries for today" is::
$ bzr log -r date:yesterday..date:today
Ancestor
--------
**ancestor**:*path*
specifies the common ancestor between the current branch,and a
different branch. This is the same ancestor that would be used for
merging purposes.
*path* may be the URL of a remote branch, or the file path to a local branch.
For example, to see what changes were made on a branch since it was forked
off **../parent**::
$ bzr diff -r ancestor:../parent
Branch
------
branch
''path'' specifies the latest revision in another branch.
''path'' may be the URL of a remote branch, or the file path to a local branch.
For example, to get the differences between this and another branch::
$ bzr diff -r branch:http://example.com/bzr/foo.dev
|