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

[Barry Warsaw]

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

On Mar 18, 2008, at 1:31 AM, Robert Collins wrote:

> On Tue, 2008-03-18 at 15:35 +0900, Stephen J. Turnbull wrote:
>> Robert Collins writes:
>>
>>> As I read the spec, if both launchpad, you, and I all generate an
>>> announce email for a given revid, we must use unique message ids.
>>
>> Spec doesn't say that.  For example, if the "important content" of  
>> the
>> message is that (a) a new commit has been added and (b) it can be
>> found in "the usual places" with the given revid, and all the users
>> agree that is true, it's ok to have multiple textually different
>> messages with the same Message-ID.
>
> Perhaps a more interesting question then, is:
> What will mail clients do with multiple messages with the same  
> message-id.

In general you do not want your system generating message-id  
collisions.  There are archivers in the wild that will just dump any  
subsequent message with a message-id it's already got.  In practice  
most duplicate message-ids are caused by spambots, so for better or  
worse, systems are beginning to filter out such duplicates.

As Stephen points out though, if you consider the copies that  
Launchpad, Robert, and Stephen generate are not "new instantiations"  
of a message, then the duplicates are fine.

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkff2agACgkQ2YZpQepbvXFfAgCgtpvb4zxNBce8aRMZsRvBwgSH
x4oAoK5PrL+HK5xkrfRSE9ucgYujG5D1
=b6lm
-----END PGP SIGNATURE-----