bzr bundle > file

[Aaron Bentley]

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

Andrew Cowie wrote:
> On Thu, 2007-08-09 at 11:32 -0400, Aaron Bentley wrote:
> Was the end result of this that `bzr bundle` would be a synonym for `bzr
> send -o stdout` ?

It currently is.  In the future, `bundle` will likely be removed, and if
not, become a subset of `send`.

>> (Though I should add that, contrary to the document, bundles and merge
>> directives are not 7-bit safe, for different reasons.  Still, attaching
>> them to mail is fine, because mail clients tend to treat attachments
>> with high-bit characters sanely.)
> 
> Yeah, we wrote that a while back. I get now that the deal with line
> ending damage.

Nothing to do with line ending damage.  Bundles and merge directives
aren't 7-bit safe, because they use 8-bit encodings.

0.9 bundles contained high-bit characters if such were present in
modified sections of files, or in the revision data.  Bundle format 0.9
explicitly used utf-8 for its metadata.  Same for Merge Directive 1.

Similarly, Merge Directive 2 may contain high-bit characters in the
preview patch, or various metadata fields (but not in the bundle, which
is base64-encoded).

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

iD8DBQFGw9+H0F+nu1YWqI0RAn26AJ4mwlnb+Lzs0ER7cGgPLxq2aTaC+wCdGTML
GyuS9POBG2KSz+XvZo/pVh0=
=KTxl
-----END PGP SIGNATURE-----