BCP for patch submittal

[Micah Cowan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I would like to provide a small how-to for people to understand how to
pull down our Mercurial repository, do some development, and submit a
patch for their changes, but it's not entirely clear to me the best way
to do this for changes that involved more than one (local) commit, but
are not large enough to make patch submittal cumbersome.

Except for cumbersomely large changes (in which case, patches or even
compressed-changeset submittal may not be the way to go), I'd prefer
that patches be sent to a mailing list set up for that purpose, and that
they be human-readable (IOW, not bundles).

I could recommend that people do their work, and when they're done, use
"hg export tip", but of course this doesn't cover multi-commit changes
against the core repo. I could recommend that they first create a local
tag after cloning the core repo, and then do an "hg export tag:tip",
which would be an improvement, but would also clutter the patch with any
changes that happened in the trunk in the meantime, that they pulled
down before preparing patches.

I could recommend that they use "hg outgoing -p <trunk>", but my
understanding is that the output format from that is not quite right for
 use with hg import, and hashes, user info, etc would be interpreted as
log info rather than metadata.

Is "hg bundle" really the only reasonable way to go? And if so, is there
a way to convert to/from bundles and export-style patches?

I realize that mq is also an option, but this seems undesirable for the
general case (plus, it's more learning for new patch submitters).

It seems like there ought to be a way to do functionally what "hg
bundle" does, but in an output format like what "hg export" does...

- --
Thanks,
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer...
http://micah.cowan.name/

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

iD8DBQFG8aHV7M8hyUobTrERCNiPAKCOk2sfpRi3wA7xzX1rrX+p7tarFgCbBlyN
YFBFk1QE3g/RRske7c3L0mY=
=2jAF
-----END PGP SIGNATURE-----