/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: John Arbash Meinel
  • Date: 2008-08-07 22:26:48 UTC
  • mto: This revision was merged to the branch mainline in revision 3614.
  • Revision ID: john@arbash-meinel.com-20080807222648-ako39zeldqibnk40
Fix the merge_sort code so that it properly increments.
We had a small bug where if you had branches descend from new
roots, as well as sub-branches within them, the branch counter
would skip, and then repeat itself. (the root was a post-increment,
while sub-branches were pre-increment.)
This changes both to be pre-increment.

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