/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/sending_changes.txt

  • Committer: Richard Wilbur
  • Date: 2016-02-04 19:07:28 UTC
  • mto: This revision was merged to the branch mainline in revision 6618.
  • Revision ID: richard.wilbur@gmail.com-20160204190728-p0zvfii6zase0fw7
Update COPYING.txt from the original http://www.gnu.org/licenses/gpl-2.0.txt  (Only differences were in whitespace.)  Thanks to Petr Stodulka for pointing out the discrepancy.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/en/user-guide/sending_changes.txt
10
10
so his/her task branches could well be inaccessible when a gatekeeper
11
11
in another timezone wants to review or merge it.
12
12
 
13
 
Breezy provides a neat feature to assist here: *merge directives*.
 
13
Bazaar provides a neat feature to assist here: *merge directives*.
14
14
 
15
15
Understanding merge directives
16
16
------------------------------
56
56
given, the directive is written to stdout.  For example::
57
57
 
58
58
  cd X-fix-123
59
 
  brz send -o ../fix-123.patch
 
59
  bzr send -o ../fix-123.patch
60
60
 
61
61
 
62
62
Applying a merge directive
66
66
using the ``merge`` and ``pull`` commands.
67
67
 
68
68
They can also be useful when communicating with upstream projects
69
 
that don't use Breezy. In particular, the preview of the overall
 
69
that don't use Bazaar. In particular, the preview of the overall
70
70
change in a merge directive looks like a vanilla software patch, so
71
71
they can be applied using ``patch -p0`` for example.