From: Carl Worth <cworth@cworth.org>
To: Michael Alan Dorman <mdorman@ironicdesign.com>, notmuch@notmuchmail.org
In-Reply-To: <20091204140946.644243f0@vimes.local>
References: <1259267025-28733-1-git-send-email-dottedmag@dottedmag.net>
	<1259788526-14205-1-git-send-email-dottedmag@dottedmag.net>
	<87zl5zfty5.fsf@yoom.home.cworth.org>
	<87k4x29732.wl%bremner@pivot.cs.unb.ca>
	<87bpiefwdq.fsf@yoom.home.cworth.org> <87aaxysjdj.fsf@vertex.dottedmag>
	<87aaxyfuz4.fsf@yoom.home.cworth.org>
	<20091204140946.644243f0@vimes.local>
Date: Fri, 04 Dec 2009 16:39:50 -0800
Message-ID: <87hbs6dzjd.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Subject: Re: [notmuch] [PATCH (rebased)] Handle message renames in mail spool
Precedence: list

--=-=-=

On Fri, 4 Dec 2009 14:09:46 -0500, Michael Alan Dorman <mdorman@ironicdesign.com> wrote:
> Besides, in notmuch, what's the difference going to be?  It'll still be
> threaded the same, etc., but you'd be able to tell that this one came
> to you rather than through the list, no?

There's one other point I should make here while talking about duplicate
messages, (as determined by identical Message ID).

Currently notmuch just indexes the first version of any given message it
sees, and simply ignores anything else it sees in the future.

We're planning to change it to at least save each of the filenames for
messages with multiple files. That way if some duplicates are deleted,
then notmuch will still be able to find one of the others.

Also, we could make notmuch index duplicate messages and add any
additional terms found to the document for the message. Currently, that
wouldn't make a big difference since notmuch is only indexing the body
and a few specific headers, (From, Subject, To, Cc, Bcc, Messsage-ID,
In-Reply-To, References).

So any differences there should be quite minor (a "[LIST]" prefix in
subject? an extra footer in the boday?), under the assumption that no
mail files will ever exist with the same message ID but disparate
content.

Now, we have a TODO item to allow for indexing additional headers,
(either by default or by user configuration). Once we start doing that,
it probably will make sense to at least index the duplicates.

But when viewing an actual message, I'm still planning on having notmuch
just return an arbitrary filename from the list of filenames associated
with that message. Does anyone see any problem with that? Can you think
of a case where you'd really care about seeing one or the other of
a particular duplicated message?

-Carl

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iD8DBQFLGavX6JDdNq8qSWgRAlrKAJ4zzMlO7WSAT5N788hnxJtSGb2h3ACfRaXG
nHhf4bQF7o6l7Q6HFQ9gkho=
=5aC2
-----END PGP SIGNATURE-----
--=-=-=--