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:
>> you are describing a set-up that's more appropriate for
>> someone who wants to become a regular contributor, not someone doing a
>> one-off bugfix.
> 
> So what I've really written is the "start contributing the first of
> potentially many bugfixes" scenario, as Talden has also noted.  Okay,
> we'll add that to the list.

Well, even if you're just submitting bugfixes, you can stick with one
branch until you need parallel branches.  My "random bugfix" branch is here:
http://code.aaronbentley.com/bzr/bzrrepo/bzr.ab

>> Also, your use of "bundle" is inaccurate.  What "bzr send" emits is a
>> "merge directive".  It may or may not contain a bundle, depending on the
>> options you give it.
> 
> Mrm.  I don't understand that yet, but hopefully I will after reading
> <some document>.

Let's start here:
$ bzr help send
Purpose: Mail or create a merge-directive for submitting changes.
...
  --no-bundle           Do not include a bundle in the merge directive.
...
  A merge directive provides many things needed for requesting merges:

  * A machine-readable description of the merge to perform

  * An optional patch that is a preview of the changes requested

  * An optional bundle of revision data, so that the changes can be applied
    directly from the merge directive, without retrieving data from a
    branch.

  If --no-bundle is specified, then public_branch is needed (and must be
  up-to-date), so that the receiver can perform the merge using the
  public_branch.  The public_branch is always included if known, so that
  people can check it later.

If that's still unclear, I guess the next place would be the
specifications for merge directives:
http://bazaar-vcs.org/Specs/MergeDirective
http://doc.bazaar-vcs.org/bzr.1.11/developers/bundle-format4.html

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

iEYEARECAAYFAkl4AxEACgkQ0F+nu1YWqI3WMwCePEVIrqnxXKkEZEqh4nPsV9X8
en0An2rPRlmZhtH0f2SORni3JS7SsAgJ
=9uTw
-----END PGP SIGNATURE-----