1 Return-Path: <beheerder@tekenbeetziekten.nl>
\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 2411C431FCB
\r
6 for <notmuch@notmuchmail.org>; Wed, 30 Jan 2013 09:15:09 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id k+ZOLhvyIx52 for <notmuch@notmuchmail.org>;
\r
16 Wed, 30 Jan 2013 09:15:05 -0800 (PST)
\r
17 Received: from srv047132.webreus.nl (srv047132.webreus.nl [46.235.47.132])
\r
18 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
\r
19 (No client certificate requested)
\r
20 by olra.theworths.org (Postfix) with ESMTPS id B6A54431FAE
\r
21 for <notmuch@notmuchmail.org>; Wed, 30 Jan 2013 09:15:04 -0800 (PST)
\r
22 Received: (qmail 19748 invoked from network); 30 Jan 2013 18:15:01 +0100
\r
23 Received: from ip73-109-210-87.adsl2.static.versatel.nl (HELO PCvangebruike)
\r
25 by srv047132.webreus.nl with SMTP; 30 Jan 2013 18:15:01 +0100
\r
26 From: "Robert Mast" <beheerder@tekenbeetziekten.nl>
\r
27 To: "'Carl Worth'" <cworth@cworth.org>, "'Jani Nikula'" <jani@nikula.org>,
\r
28 <notmuch@notmuchmail.org>
\r
29 References: <000001cdfcd9$82500f00$86f02d00$@nl> <87wquxjq7k.fsf@nikula.org>
\r
30 <002601cdfd83$83b283f0$8b178bd0$@nl>
\r
31 <87boc8bt8a.fsf@yoom.home.cworth.org>
\r
32 In-Reply-To: <87boc8bt8a.fsf@yoom.home.cworth.org>
\r
33 Subject: RE: Reply all - issue
\r
34 Date: Wed, 30 Jan 2013 18:14:48 +0100
\r
35 Message-ID: <00bf01cdff0d$4ecedd10$ec6c9730$@nl>
\r
37 Content-Type: text/plain;
\r
39 Content-Transfer-Encoding: 7bit
\r
40 X-Mailer: Microsoft Office Outlook 12.0
\r
41 Thread-Index: Ac39yr2ciHq/BzOAQieJla7aevASjQBP0GPg
\r
42 Content-Language: nl
\r
43 X-BeenThere: notmuch@notmuchmail.org
\r
44 X-Mailman-Version: 2.1.13
\r
46 List-Id: "Use and development of the notmuch mail system."
\r
47 <notmuch.notmuchmail.org>
\r
48 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
49 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
50 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
51 List-Post: <mailto:notmuch@notmuchmail.org>
\r
52 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
53 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
54 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
55 X-List-Received-Date: Wed, 30 Jan 2013 17:15:09 -0000
\r
57 Thanks for your clear explanation.
\r
59 The thread-merging and breaking is in the procedure already pointed at by
\r
60 Jani: (_notmuch_database_link_message() in lib/database.cc.)
\r
62 Is there a quick way to recognize those git-threads by subject-syntax, or to
\r
63 reliably tag them to exclude them from subject-breaking?
\r
68 -----Oorspronkelijk bericht-----
\r
69 Van: Carl Worth [mailto:cworth@cworth.org]
\r
70 Verzonden: dinsdag 29 januari 2013 3:48
\r
71 Aan: Robert Mast; 'Jani Nikula'; notmuch@notmuchmail.org
\r
72 Onderwerp: RE: Reply all - issue
\r
75 Is there any existing thread-breaking? There wasn't the last time I looked
\r
76 at the code closely, (but admittedly, that was a while ago).
\r