2977.1.5
by Ian Clatworthy
added chapter on Sharing with a peer |
1 |
Annotating changes |
2 |
================== |
|
3 |
||
4 |
Seeing the origin of content |
|
5 |
---------------------------- |
|
6 |
||
7 |
When two or more people are working on files, it can be highly |
|
8 |
useful at times to see who created or last changed certain content. |
|
9 |
To do this, using the annotate command like this:: |
|
10 |
||
11 |
bzr annotate readme.txt |
|
12 |
||
13 |
If you are a pessimist or an optimist, you might prefer to use |
|
14 |
one of built-in aliases for ``annotate``: ``blame`` or ``praise``. |
|
15 |
Either way, this displays each line of the file together with |
|
16 |
information such as: |
|
17 |
||
18 |
* who changed it last |
|
19 |
* when it was last changed |
|
20 |
* the commit message. |
|
21 |
||
22 |
GUI tools |
|
23 |
--------- |
|
24 |
||
25 |
The various GUI plugins for Bazaar provide graphical tools for |
|
26 |
viewing annotation information. For example, the bzr-gtk plugin |
|
27 |
provides a GUI tool for this that can be launched using the |
|
28 |
``gannotate`` command:: |
|
29 |
||
30 |
bzr gannotate readme.txt |
|
31 |
||
32 |
The GUI tools typically provide a much richer display of |
|
33 |
interesting information (e.g. all the changes in each commit) |
|
3309.1.1
by Ian Clatworthy
Reduce evangelism in the User Guide |
34 |
so you may prefer them over the text-based command. |
2977.1.5
by Ian Clatworthy
added chapter on Sharing with a peer |
35 |