← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

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

  • Committer: Danny van Heumen
  • Date: 2010-03-09 21:42:11 UTC
  • mto: (4634.139.5 2.0)
  • mto: This revision was merged to the branch mainline in revision 5160.
  • Revision ID: danny@dannyvanheumen.nl-20100309214211-iqh42x6qcikgd9p3
Reverted now-useless TODO list.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/en/user-guide/reviewing_changes.txt
8
8
prior to permanently recording it. This way, you can make sure you'll be
9
9
committing what you intend to.
10
10
 
11
 
Two bzr commands are particularly useful here: **status** and **diff**.
 
11
Two bzr commands are particularly useful here: **status** and **diff**.  
12
12
 
13
13
bzr status
14
14
----------
45
45
    % bzr diff -r 1000..          # everything since r1000
46
46
    % bzr diff -r 1000..1100      # changes from 1000 to 1100
47
47
 
48
 
To see the changes introduced by a single revision, you can use the ``-c``
49
 
option to diff.
50
 
 
51
 
::
52
 
 
53
 
    % bzr diff -c 1000            # changes from r1000
54
 
                                  # identical to -r999..1000
55
 
 
56
48
The ``--diff-options`` option causes bzr to run the external diff program,
57
49
passing options.  For example::
58
50
 
61
53
Some projects prefer patches to show a prefix at the start of the path
62
54
for old and new files.  The ``--prefix`` option can be used to provide
63
55
such a prefix.
64
 
As a shortcut, ``bzr diff -p1`` produces a form that works with the
 
56
As a shortcut, ``bzr diff -p1`` produces a form that works with the 
65
57
command ``patch -p1``.
66
58