1 Return-Path: <madduck@lapse.rw.madduck.net>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id AA37F431FBC
\r
6 for <notmuch@notmuchmail.org>; Thu, 7 Jan 2010 19:12:46 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
8 Received: from olra.theworths.org ([127.0.0.1])
\r
9 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
10 with ESMTP id 8pq-wufSS7Mp for <notmuch@notmuchmail.org>;
\r
11 Thu, 7 Jan 2010 19:12:46 -0800 (PST)
\r
12 Received: from clegg.madduck.net (clegg.madduck.net [193.242.105.96])
\r
13 by olra.theworths.org (Postfix) with ESMTP id 0504D431FAE
\r
14 for <notmuch@notmuchmail.org>; Thu, 7 Jan 2010 19:12:46 -0800 (PST)
\r
15 Received: from lapse.rw.madduck.net (lapse.nz.madduck.net
\r
16 [IPv6:2001:4428:234::1])
\r
17 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
\r
18 (Client CN "lapse.rw.madduck.net",
\r
19 Issuer "CAcert Class 3 Root" (verified OK))
\r
20 by clegg.madduck.net (postfix) with ESMTPS id 87F011D4097
\r
21 for <notmuch@notmuchmail.org>; Fri, 8 Jan 2010 04:12:41 +0100 (CET)
\r
22 Received: by lapse.rw.madduck.net (Postfix, from userid 1000)
\r
23 id A3B0E809C; Fri, 8 Jan 2010 16:12:38 +1300 (NZDT)
\r
24 Date: Fri, 8 Jan 2010 16:12:38 +1300
\r
25 From: martin f krafft <madduck@madduck.net>
\r
26 To: notmuch <notmuch@notmuchmail.org>
\r
27 Message-ID: <20100108031238.GD23442@lapse.rw.madduck.net>
\r
28 Mail-Followup-To: notmuch <notmuch@notmuchmail.org>
\r
30 Content-Type: multipart/signed; micalg=pgp-ripemd160;
\r
31 protocol="application/pgp-signature"; boundary="fOHHtNG4YXGJ0yqR"
\r
32 Content-Disposition: inline
\r
33 In-Reply-To: <3wdzl59mjik.fsf@testarossa.amd.com>
\r
34 <87my1kkzbn.fsf@marten.i-did-not-set--mail-host-address--so-tickle-me>
\r
35 <87ocm64ivu.fsf@yoom.home.cworth.org>
\r
36 <87ljha3avx.fsf@home.veldthuis.com>
\r
37 <87ws0ug23f.fsf@yoom.home.cworth.org>
\r
38 <1260400470-sup-5775@testarossa>
\r
39 X-Motto: Keep the good times rollin'
\r
40 X-OS: Debian GNU/Linux squeeze/sid kernel 2.6.32-trunk-686 i686
\r
41 X-Spamtrap: madduck.bogus@madduck.net
\r
42 X-Subliminal-Message: debian/rules!
\r
43 User-Agent: Mutt/1.5.20 (2009-06-14)
\r
44 X-Virus-Scanned: clamav-milter 0.95.3 at clegg
\r
45 X-Virus-Status: Clean
\r
46 Subject: Re: [notmuch] Threading
\r
47 X-BeenThere: notmuch@notmuchmail.org
\r
48 X-Mailman-Version: 2.1.13
\r
50 List-Id: "Use and development of the notmuch mail system."
\r
51 <notmuch.notmuchmail.org>
\r
52 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
53 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
54 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
55 List-Post: <mailto:notmuch@notmuchmail.org>
\r
56 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
57 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
58 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
59 X-List-Received-Date: Fri, 08 Jan 2010 03:12:46 -0000
\r
63 Content-Type: text/plain; charset=us-ascii
\r
64 Content-Disposition: inline
\r
65 Content-Transfer-Encoding: quoted-printable
\r
67 also sprach Carl Worth <cworth@cworth.org> [2009.12.11.0639 +1300]:
\r
68 > On Wed, 9 Dec 2009 16:21:34 -0700, Mark Anderson <markr.anderson@amd.com>=
\r
70 > > I was wondering if there's a way in notmuch to group un-associated
\r
71 > > threads into a single thread.
\r
73 > There's certainly nothing like that in notmuch currently.
\r
75 > Sup had user-level functionality in the interface for stitching
\r
76 > messages into a single thread, and I definitely think that that
\r
77 > doesn't make any sense.
\r
79 Why doesn't it make sense? Mutt does it too, and stitching means
\r
80 actually (re)writing In-Reply-To and References headers.
\r
82 I think this is one of the most useful "productivity features" in
\r
85 I also think that threading is a preference thing. As Carl said in
\r
88 > Just this morning I sent a mail to the notmuch list, which was
\r
89 > a reply, (and legitimately so), but also potentially of interest
\r
90 > to everyone on the list, (since it was regarding a bug fix
\r
91 > unrelated to the original topic of the thread I was replying to).
\r
93 > So I was stuck on whether I should break the thread or not, (at
\r
94 > the sending end). I guess I could have just sent a quick "this is
\r
95 > pushed" reply, and independently composed a separate message
\r
96 > telling people about the fix.
\r
98 > I ended up keeping the threading intact in that case, (which
\r
99 > I think is right).
\r
101 I often thread forwarded messages (and their followups) with the
\r
102 thread because all my information management currently is
\r
105 I think being able to freely break and tie threads in a trivial way
\r
106 is a definite plus!
\r
108 > But I still have a hard time justifying user operations to
\r
109 > manipulate threading. The whole point of threading is to make it
\r
110 > faster to process and read messages. But manual operations like
\r
111 > joining and splitting threads seem like the user just doing more
\r
112 > work, and that *after* having read the messages. So that seems
\r
113 > mostly backwards to me.
\r
115 Reading is one thing. Information storage and organisation is
\r
116 another. After a message is delivered (and read) to my mailbox, it's
\r
117 really mine and I can (and should be able) to affix it and integrate
\r
118 it into my organisational scheme any way I want, don't you think?
\r
121 martin | http://madduck.net/ | http://two.sentenc.es/
\r
123 "if there's anything more important than my ego,
\r
124 i want it caught and shot now."
\r
125 -- zaphod beeblebrox
\r
127 spamtraps: madduck.bogus@madduck.net
\r
130 Content-Type: application/pgp-signature; name="digital_signature_gpg.asc"
\r
131 Content-Description: Digital signature (see http://martin-krafft.net/gpg/)
\r
132 Content-Disposition: inline
\r
134 -----BEGIN PGP SIGNATURE-----
\r
135 Version: GnuPG v1.4.10 (GNU/Linux)
\r
137 iEYEAREDAAYFAktGoqYACgkQIgvIgzMMSnVMDQCgtMy9gnEnA5lZnBtmqfSApfiM
\r
138 pJ0An2teX/uyJ9MD5YVXgz2tQLLk/teo
\r
140 -----END PGP SIGNATURE-----
\r
142 --fOHHtNG4YXGJ0yqR--
\r