~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

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

  • Committer: John Arbash Meinel
  • Date: 2009-12-02 23:09:40 UTC
  • mfrom: (4853.1.1 whitespace)
  • mto: This revision was merged to the branch mainline in revision 4856.
  • Revision ID: john@arbash-meinel.com-20091202230940-7n2aydoxngdqxzld
Strip trailing whitespace from doc files by Patrick Regan.

Resolve one small conflict with another doc edit.
Also, revert the changes to all the .pdf and .png files. We shouldn't
be touching them as they are pure-binary files.

Show diffs side-by-side

added added

removed removed

Lines of Context:
34
34
Creating a merge directive
35
35
--------------------------
36
36
 
37
 
To create and optionally send a merge directive, use the ``send`` command. 
 
37
To create and optionally send a merge directive, use the ``send`` command.
38
38
 
39
39
By default, ``send`` will email the merge directive to the "submission
40
40
address" for the branch, which is typically the lead developer or the
41
 
development mailing list.  
 
41
development mailing list.
42
42
``send`` without options will create a merge directive, fire up your email
43
43
tool and attach it, ready for you to add the explanatory text bit.
44
44
(See the online help for ``send`` and