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

[Robert Collins]

On Mon, 2008-03-17 at 16:04 -0500, John Arbash Meinel wrote:
> -----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"?

I don't think its legal to send two different messages with the same
message id. Which could happen with multiple announcements. so -1 on
this, but perhaps the concept can be used somehow still.

-Rob
-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20080318/194f7257/attachment.pgp