← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

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

  • Committer: Ian Clatworthy
  • Date: 2010-02-19 03:02:07 UTC
  • mto: (4797.23.1 integration-2.1)
  • mto: This revision was merged to the branch mainline in revision 5055.
  • Revision ID: ian.clatworthy@canonical.com-20100219030207-zpbzx021zavx4sqt
What's New in 2.1 - a summary of changes since 2.0

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/en/user-guide/sending_changes.txt
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