[MERGE] Revised mini-tutorial

[Aaron Bentley]

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

Matthew Revell wrote:
> Hi all,
> 
> I've fleshed out the mini-tutorial somewhat and, perhaps, pitched it
> at a slightly less experienced reader. I've also moved the "creating a
> personal branch" sections to the end.
> 
> This is my first BundleBuggy message so go easy on me if I get it wrong :-)

Okay, I'll go easy on ya.

BundleBuggy only looks for patches in attachments, not in message
bodies.  So your patch isn't being shown as a patch in Bundle Buggy.

It's also nice to send merge directives or bundles, because Bundle Buggy
can track those better (hence the name).  They are also nicer for the
person who eventually merges your patch, because they preserve metadata.

The patch that you sent looks like it used to be a bundle, but had the
top stripped off it.  Stripping that metadata loses the advantages
bundles provide.

I should also mention that "bzr send", in 0.91, will do all the hard
work for you.  It will create a merge directive, start your mail client,
and compose a new message with that attachment.  On *nix, this uses
xdg-email from the xdg-utils package.

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

iD8DBQFG/W9m0F+nu1YWqI0RAhq/AJsFGuvgDYSTDmEzy0E/7CRhKz+rzwCcDAk7
hFYfTIZlbb06y8dWkSAEkgg=
=Jvyn
-----END PGP SIGNATURE-----