/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: 2009-06-17 19:08:25 UTC
  • mto: This revision was merged to the branch mainline in revision 4460.
  • Revision ID: john@arbash-meinel.com-20090617190825-ktfk82li57rf2im6
It seems that fetch() no longer returns the number of revisions fetched.
It still does for *some* InterRepository fetch paths, but the generic one does not.
It is also not easy to get it to, since the Source and Sink are the ones
that would know how many keys were transmitted, and they are potentially 'remote'
objects.

This was also only tested to occur as a by-product in a random 'test_commit' test.
I assume if we really wanted the assurance, we would have a per_repo or interrepo
test for it.

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