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

[John Arbash Meinel]

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

Barry Warsaw wrote:
| 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
|

Well, I was thinking to use something like:

john.arbash-meinel.com-234234-2342342 at bazaar

or given this discussion thread maybe

john_40arbash-meinel.com-234234-2342342 at bzr-email

So that if Launchpad wants to generate a similar e-mail, they can use @launchpad.

If we wanted we could make a it something like @commit.bzr-email. To make it
clear that it was a separate action from push/pull.

There are certainly things I could do to make them more unique. But the *point*
was to have them such that 2 clients could create threads for eachother. So that
if Robert commits a patch that I then build upon, you can follow that thread.

And you could see which pqm revision the work was done against, etc.

You can also have multiple entries in the "In-Reply-To" so if we wanted to we
could have:

Message-id: <mycommit at bzr-email>
In-Reply-To: <myparent_commit at bzr-email> <myparent_commit at launchpad>

etc. Though in the bzr-email case I would actually expect launchpad to be the
one referencing possible bzr-email commits, rather than the other way around.

John
=:->

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

iD8DBQFH39yYJdeBCYSNAAMRAraRAKDGNXNrfNiefM9Mxrq1xy1kpVIZGACdGlMr
PWqGJjhEvdzTd/0zuWA36vU=
=8gGN
-----END PGP SIGNATURE-----