bzr send: what is the bundle part ?

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Xavier Maillard wrote:
>    > If you do "bzr send --no-bundle", then you must supply the location of a
>    > public copy of your branch (or bzr must already know the public
>    > location).  bzr will verify that the relevant revisions are present in
>    > that branch.  bzr merge and pull will work fine if you do this.
> 
>    Oops, right.  I forgot that bzr would attempt to DTRT when the branch is
>    accessible.  I should have said that if there's no bundle and you're offline but
>    the branch is on the network, then you can't do “bzr merge MERGE_DIRECTIVE_FILE”
>    successfully (whereas if the bundle is present, then all the data needed is
>    right there in the merge directive).
> 
> Does this mean we _must_ enclosed the bundle part in our merge
> request for the bazaar project ?

No.  You could publish a branch and use the --no-bundle option.  Or you
can send a patch.

Manually stripping the bundle off a merge directive would be
counterproductive, as it would produce an unmergeable "merge directive".

However, we do *prefer* that you send a merge directive with a bundle.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH8tki0F+nu1YWqI0RArgEAJ9aAN5WL8m7IZ/eigSJEVdUFRvNvwCfYJA7
Fq5QN1YIFQLTADObjTD5yuw=
=Gf3S
-----END PGP SIGNATURE-----