From: Jameson Graef Rollins <jrollins@finestructure.net>
To: David Bremner <david@tethera.net>,
	Robert Mast <beheerder@tekenbeetziekten.nl>,
	'Carl Worth' <cworth@cworth.org>,
	'Jani Nikula' <jani@nikula.org>, notmuch@notmuchmail.org
Subject: RE: Reply all - issue
In-Reply-To: <87r4l2kvak.fsf@zancas.localnet>
References: <000001cdfcd9$82500f00$86f02d00$@nl> <87wquxjq7k.fsf@nikula.org>
	<002601cdfd83$83b283f0$8b178bd0$@nl>
	<87boc8bt8a.fsf@yoom.home.cworth.org>
	<000001cdff33$afe11070$0fa33150$@nl>
	<87txpykve8.fsf@zancas.localnet> <87r4l2kvak.fsf@zancas.localnet>
User-Agent: Notmuch/0.15+8~gd4a7374 (http://notmuchmail.org) Emacs/24.2.1
	(x86_64-pc-linux-gnu)
Date: Mon, 11 Feb 2013 23:07:50 -0800
Message-ID: <87sj52nh6h.fsf@servo.finestructure.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha256; protocol="application/pgp-signature"
Precedence: list

--=-=-=
Content-Type: text/plain

On Wed, Jan 30 2013, David Bremner <david@tethera.net> wrote:
> Let me step back a level and say that special casing git patch series
> strikes me as not yet seeing the problem in enough generality. Others
> might disagree, of course.

I agree with this statement.

So I encounter the thread hijacking problem occasionally, but not
frequently enough that I would trust a particular heuristic to cover it.
I think I would prefer to just split hijacked threads manually as I
encounter them.

Just a thought: what if messages with a given tag (e.g. "new-thread")
were always treated as the source of a new thread?  A message with the
given tag could just be (re)indexed with any In-Reply-To/References
headers stripped before indexing.  This would allow users to break
threads manually, and it would mean dump && restore would always return
the same state.

The actual thread breaking, or specifically where it happens, would have
to be thought through a bit.  Maybe this could be rolled into notmuch
new somehow?  Or some other top-level function that applies operations
to messages based on tags?

jamie.

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRGepGAAoJEO00zqvie6q8ww0P+wfU3lZnpzMeX2xsygDyhrfv
uxguQYOx744Nb3boVqkrKasRpJuuTXGkoyBvtnFHAD3EyExP1h/uE7YWBo8AULzd
kxBgZdney4Z4UCxxPJpe4XJNjIEwTbuOR1691SU07GFshewI79/urC9jqiocUytO
b6UhvwBXzK3qcqKgBgRmEYqO1V6Av7RdFjBSbL/ZiYn0nOc4y4oUi2dh2kB2gWeC
n4YOsI1t2qV9b2Y+36SXBV7omX1a42CQJHLH/6mtGd2Oo3imIqdzsTW3kyZAhuJQ
smBt4sxjYA79gvgUTlmw6tYIje2qhDbWbHFDUbb0kz0aZEqB4q+i04n5m4vdT4N3
7lvoG/IHnQWI1LDX81n9DoaISbfJ36WyUU3151izHt/0l12cGpP/CAynG1jGziRx
N2iq4DBWlqQBKno/qNnSMY9usvnoA9beX9q4hMVg7S/YnDQk1lK1ux95oPfYtLDd
g/EUEDgMFwia4Dft6Q9yCG1v0IQP9Q3R2VDTshgXv0NutQg/Benj70EDZVaQZbbs
kdCB8xo3RRTUWPkAVk8lUoe6zrLPlrkhQknFPkFHxgkvBVwALceNBSwvxL0IChch
XaG9qukYgqrlh+Fly3dqXY97m6rhbT57EyALHJCYgSjPOCw9LXcxkRB8TvT6TLkS
OXps5gD/O80wf9MV7hK7
=7S0Z
-----END PGP SIGNATURE-----
--=-=-=--