RE: Reply all - issue

diff --git a/6b/fb3b83221cf7f8a85ad18564eb00a4f85d0b8d b/6b/fb3b83221cf7f8a85ad18564eb00a4f85d0b8d
new file mode 100644 (file)
index 0000000..12ebb0d
--- /dev/null
+++ b/6b/fb3b83221cf7f8a85ad18564eb00a4f85d0b8d
@@ -0,0 +1,110 @@
+Return-Path: <beheerder@tekenbeetziekten.nl>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 5077D431FC0\r
+       for <notmuch@notmuchmail.org>; Wed, 30 Jan 2013 12:57:18 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 0\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]\r
+       autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id 3aMP9Zlm4Eko for <notmuch@notmuchmail.org>;\r
+       Wed, 30 Jan 2013 12:57:15 -0800 (PST)\r
+Received: from srv047132.webreus.nl (srv047132.webreus.nl [46.235.47.132])\r
+       (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 6DB81431FAE\r
+       for <notmuch@notmuchmail.org>; Wed, 30 Jan 2013 12:57:15 -0800 (PST)\r
+Received: (qmail 26515 invoked from network); 30 Jan 2013 21:57:12 +0100\r
+Received: from ip73-109-210-87.adsl2.static.versatel.nl (HELO PCvangebruike)\r
+       (87.210.109.73)\r
+       by srv047132.webreus.nl with SMTP; 30 Jan 2013 21:57:09 +0100\r
+From: "Robert Mast" <beheerder@tekenbeetziekten.nl>\r
+To: "'Carl Worth'" <cworth@cworth.org>, "'Jani Nikula'" <jani@nikula.org>,\r
+       <notmuch@notmuchmail.org>\r
+References: <000001cdfcd9$82500f00$86f02d00$@nl> <87wquxjq7k.fsf@nikula.org>\r
+       <002601cdfd83$83b283f0$8b178bd0$@nl>\r
+       <87boc8bt8a.fsf@yoom.home.cworth.org> \r
+In-Reply-To: \r
+Subject: RE: Reply all - issue\r
+Date: Wed, 30 Jan 2013 21:56:59 +0100\r
+Message-ID: <000001cdff2c$59262b50$0b7281f0$@nl>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain;\r
+       charset="us-ascii"\r
+Content-Transfer-Encoding: 7bit\r
+X-Mailer: Microsoft Office Outlook 12.0\r
+Thread-Index: Ac39yr2ciHq/BzOAQieJla7aevASjQBP0GPgAAf4vDA=\r
+Content-Language: nl\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Wed, 30 Jan 2013 20:57:18 -0000\r
+\r
+I never used git for mailpatching, so I have no example-mailbox to analyse.\r
+\r
+I understand that the subject starting with "[PATCH <anything>]" can be a\r
+git-hint, but is not guaranteed. Or is it? [1]\r
+\r
+If it isn't, can I assume all git-messages comply to this set: [2]\r
+\r
+"The patch is expected to be inline, directly following the message. Any\r
+line that is of the form: \r
+\r
+. three-dashes and end-of-line, or \r
+. a line that begins with "diff -", or \r
+. a line that begins with "Index: "\r
+"\r
+\r
+Or should the git filter also look for a "scissor-line" [3] to identify a\r
+git-message?\r
+\r
+[1] http://www.kernel.org/pub/software/scm/git/docs/git-send-email.html\r
+[2] http://linux.die.net/man/1/git-am \r
+[3] http://linux.die.net/man/1/git-mailinfo \r
+\r
+Or are there any guaranteed under water git-markers in the mailheader?\r
+\r
+-----Oorspronkelijk bericht-----\r
+Van: Robert Mast [mailto:beheerder@tekenbeetziekten.nl] \r
+Verzonden: woensdag 30 januari 2013 18:15\r
+Aan: 'Carl Worth'; 'Jani Nikula'; 'notmuch@notmuchmail.org'\r
+Onderwerp: RE: Reply all - issue\r
+\r
+Thanks for your clear explanation.\r
+\r
+The thread-merging and breaking is in the procedure already pointed at by\r
+Jani: (_notmuch_database_link_message() in lib/database.cc.)\r
+\r
+Is there a quick way to recognize those git-threads by subject-syntax, or to\r
+reliably tag them to exclude them from subject-breaking?\r
+\r
+\r
+\r
+\r
+-----Oorspronkelijk bericht-----\r
+Van: Carl Worth [mailto:cworth@cworth.org] \r
+Verzonden: dinsdag 29 januari 2013 3:48\r
+Aan: Robert Mast; 'Jani Nikula'; notmuch@notmuchmail.org\r
+Onderwerp: RE: Reply all - issue\r
+\r
+\r
+Is there any existing thread-breaking? There wasn't the last time I looked\r
+at the code closely, (but admittedly, that was a while ago).\r
+\r
+-Carl\r
+\r
+\r