Short, task-based bzr doclets for real-world use cases.

[Aaron Bentley]

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

Karl Fogel wrote:
> Aaron Bentley <aaron at aaronbentley.com> writes:
>>> Mrm.  I don't understand that yet, but hopefully I will after reading
>>> <some document>.
>> Let's start here:
>> $ bzr help send
> 
> Thanks.  (I wasn't actually confused about where to go, I was just
> mentioning that I hadn't been there yet :-) ).

Oh, I thought you weren't sure whether there were any docs to look at.

> So it sounds like the "bundle" is the non-human-readable portion at the
> end of the output generated by default by 'bzr send'?

Right.  Everything from "# Begin bundle" to EOF.

The history is that bzr gained bundle support first, sort of inferring
the requested merge from the bundle's tip revision.  Separately, we had
a specialized format for requesting merges via PQM.  Then I came up with
"merge directives", which unify these cases and make things explicit,
e.g. with cherrypicks.  Bundle Buggy was named before this.

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

iEYEARECAAYFAkl4f1EACgkQ0F+nu1YWqI0S/ACfcff6Cju8ZvCNKhpxPHSrfgLc
YC0AniYe3iqT/j6qAqqOinNZZRMeobyE
=8S7H
-----END PGP SIGNATURE-----