[RFC] 'bzr-email' using revision_id for threading

[John Arbash Meinel]

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

I was just discussing this at pycon. But wouldn't it be neat if you
could read "bazaar-commits" in threaded mode, and have it trace back the
different branches where the commits happened.

And then I realized... why not use the revision-id as the "message-id".
We are generating the emails ourselves, so it seems like it would work.

You could just set:

Message-Id: <bazaar-revision-id>

And then you set:
References: <bazaar-parent-id>

I'm going to poke around and see if I can get it to work. But does
anyone have an idea about what is legal in "References/Message-ID"?

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

iD8DBQFH3tz3JdeBCYSNAAMRAhbcAJ9+bKrLqRhSHDpr/QviOS/1TvPpawCdE1dT
MGPR8pmUbDJ9kIQE57Vr9qU=
=ifRX
-----END PGP SIGNATURE-----