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 D1749431FAF
\r
6 for <notmuch@notmuchmail.org>; Wed, 30 Jan 2013 13:49:48 -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 2cGqOQSF0tSP for <notmuch@notmuchmail.org>;
\r
16 Wed, 30 Jan 2013 13:49:45 -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 71D8B431FAE
\r
21 for <notmuch@notmuchmail.org>; Wed, 30 Jan 2013 13:49:45 -0800 (PST)
\r
22 Received: (qmail 1736 invoked from network); 30 Jan 2013 22:49:44 +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 22:49:41 +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
33 Subject: RE: Reply all - issue
\r
34 Date: Wed, 30 Jan 2013 22:49:31 +0100
\r
35 Message-ID: <000001cdff33$afe11070$0fa33150$@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/BzOAQieJla7aevASjQBP0GPgAAf4vDAAAUOMgA==
\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 21:49:49 -0000
\r
57 I ran git send-email and became the following line in the mail-header:
\r
59 "X-Mailer: git-send-email 1.7.9.5"
\r
61 I see that this git-marker already existed in version 1.3 in 2006:
\r
63 http://comments.gmane.org/gmane.comp.version-control.git/23337
\r
65 Can I assume, apart from the version number, that this header-marker applies
\r
66 to all git-mail that should not be subject-splitted?
\r
68 I can also leave the threads in the database as they are and only change
\r
69 notmuch_query_search_threads in lib/query.cc to add the subject as a second
\r
70 hash-key and notmuch_threads_get/_notmuch_thread_create for also looking for
\r
71 the subject of the seed-message.
\r
73 Then I only have to add the stripped subject as a search-term. The subject
\r
74 that's now in the database is the original non-stripped subject.
\r
76 I expect next weekend to have some time again.
\r
78 -----Oorspronkelijk bericht-----
\r
79 Van: Robert Mast [mailto:beheerder@tekenbeetziekten.nl]
\r
80 Verzonden: woensdag 30 januari 2013 21:57
\r
81 Aan: 'Carl Worth'; 'Jani Nikula'; 'notmuch@notmuchmail.org'
\r
82 Onderwerp: RE: Reply all - issue
\r
84 I never used git for mailpatching, so I have no example-mailbox to analyse.
\r
86 I understand that the subject starting with "[PATCH <anything>]" can be a
\r
87 git-hint, but is not guaranteed. Or is it? [1]
\r
89 If it isn't, can I assume all git-messages comply to this set: [2]
\r
91 "The patch is expected to be inline, directly following the message. Any
\r
92 line that is of the form:
\r
94 . three-dashes and end-of-line, or
\r
95 . a line that begins with "diff -", or
\r
96 . a line that begins with "Index: "
\r
99 Or should the git filter also look for a "scissor-line" [3] to identify a
\r
102 [1] http://www.kernel.org/pub/software/scm/git/docs/git-send-email.html
\r
103 [2] http://linux.die.net/man/1/git-am
\r
104 [3] http://linux.die.net/man/1/git-mailinfo
\r
106 Or are there any guaranteed under water git-markers in the mailheader?
\r
108 -----Oorspronkelijk bericht-----
\r
109 Van: Robert Mast [mailto:beheerder@tekenbeetziekten.nl]
\r
110 Verzonden: woensdag 30 januari 2013 18:15
\r
111 Aan: 'Carl Worth'; 'Jani Nikula'; 'notmuch@notmuchmail.org'
\r
112 Onderwerp: RE: Reply all - issue
\r
114 Thanks for your clear explanation.
\r
116 The thread-merging and breaking is in the procedure already pointed at by
\r
117 Jani: (_notmuch_database_link_message() in lib/database.cc.)
\r
119 Is there a quick way to recognize those git-threads by subject-syntax, or to
\r
120 reliably tag them to exclude them from subject-breaking?
\r
125 -----Oorspronkelijk bericht-----
\r
126 Van: Carl Worth [mailto:cworth@cworth.org]
\r
127 Verzonden: dinsdag 29 januari 2013 3:48
\r
128 Aan: Robert Mast; 'Jani Nikula'; notmuch@notmuchmail.org
\r
129 Onderwerp: RE: Reply all - issue
\r
132 Is there any existing thread-breaking? There wasn't the last time I looked
\r
133 at the code closely, (but admittedly, that was a while ago).
\r