/brz/remove-bazaar

To get this branch, use:
bzr branch http://gegoxaren.bato24.eu/bzr/brz/remove-bazaar

« back to all changes in this revision

Viewing changes to doc/en/user-guide/annotating_changes.txt

  • Committer: Robert Collins
  • Date: 2010-05-06 23:41:35 UTC
  • mto: This revision was merged to the branch mainline in revision 5223.
  • Revision ID: robertc@robertcollins.net-20100506234135-yivbzczw1sejxnxc
Lock methods on ``Tree``, ``Branch`` and ``Repository`` are now
expected to return an object which can be used to unlock them. This reduces
duplicate code when using cleanups. The previous 'tokens's returned by
``Branch.lock_write`` and ``Repository.lock_write`` are now attributes
on the result of the lock_write. ``repository.RepositoryWriteLockResult``
and ``branch.BranchWriteLockResult`` document this. (Robert Collins)

``log._get_info_for_log_files`` now takes an add_cleanup callable.
(Robert Collins)

Show diffs side-by-side

added added

removed removed

Lines of Context:
8
8
useful at times to see who created or last changed certain content.
9
9
To do this, using the annotate command like this::
10
10
 
11
 
  brz annotate readme.txt
 
11
  bzr annotate readme.txt
12
12
 
13
13
If you are a pessimist or an optimist, you might prefer to use
14
14
one of built-in aliases for ``annotate``: ``blame`` or ``praise``.
22
22
GUI tools
23
23
---------
24
24
 
25
 
The various GUI plugins for Breezy provide graphical tools for
26
 
viewing annotation information. For example, the brz-gtk plugin
 
25
The various GUI plugins for Bazaar provide graphical tools for
 
26
viewing annotation information. For example, the bzr-gtk plugin
27
27
provides a GUI tool for this that can be launched using the
28
28
``gannotate`` command::
29
29
 
30
 
  brz gannotate readme.txt
 
30
  bzr gannotate readme.txt
31
31
 
32
32
The GUI tools typically provide a much richer display of
33
33
interesting information (e.g. all the changes in each commit)