Return-Path: <beheerder@tekenbeetziekten.nl>
X-Original-To: notmuch@notmuchmail.org
Delivered-To: notmuch@notmuchmail.org
Received: from localhost (localhost [127.0.0.1])
	by olra.theworths.org (Postfix) with ESMTP id 5077D431FC0
	for <notmuch@notmuchmail.org>; Wed, 30 Jan 2013 12:57:18 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
	autolearn=disabled
Received: from olra.theworths.org ([127.0.0.1])
	by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 3aMP9Zlm4Eko for <notmuch@notmuchmail.org>;
	Wed, 30 Jan 2013 12:57:15 -0800 (PST)
Received: from srv047132.webreus.nl (srv047132.webreus.nl [46.235.47.132])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by olra.theworths.org (Postfix) with ESMTPS id 6DB81431FAE
	for <notmuch@notmuchmail.org>; Wed, 30 Jan 2013 12:57:15 -0800 (PST)
Received: (qmail 26515 invoked from network); 30 Jan 2013 21:57:12 +0100
Received: from ip73-109-210-87.adsl2.static.versatel.nl (HELO PCvangebruike)
	(87.210.109.73)
	by srv047132.webreus.nl with SMTP; 30 Jan 2013 21:57:09 +0100
From: "Robert Mast" <beheerder@tekenbeetziekten.nl>
To: "'Carl Worth'" <cworth@cworth.org>, "'Jani Nikula'" <jani@nikula.org>,
	<notmuch@notmuchmail.org>
References: <000001cdfcd9$82500f00$86f02d00$@nl> <87wquxjq7k.fsf@nikula.org>
	<002601cdfd83$83b283f0$8b178bd0$@nl>
	<87boc8bt8a.fsf@yoom.home.cworth.org> 
In-Reply-To: 
Subject: RE: Reply all - issue
Date: Wed, 30 Jan 2013 21:56:59 +0100
Message-ID: <000001cdff2c$59262b50$0b7281f0$@nl>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac39yr2ciHq/BzOAQieJla7aevASjQBP0GPgAAf4vDA=
Content-Language: nl
X-BeenThere: notmuch@notmuchmail.org
X-Mailman-Version: 2.1.13
Precedence: list
List-Id: "Use and development of the notmuch mail system."
	<notmuch.notmuchmail.org>
List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
List-Archive: <http://notmuchmail.org/pipermail/notmuch>
List-Post: <mailto:notmuch@notmuchmail.org>
List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jan 2013 20:57:18 -0000

I never used git for mailpatching, so I have no example-mailbox to analyse.

I understand that the subject starting with "[PATCH <anything>]" can be a
git-hint, but is not guaranteed. Or is it? [1]

If it isn't, can I assume all git-messages comply to this set: [2]

"The patch is expected to be inline, directly following the message. Any
line that is of the form: 

. three-dashes and end-of-line, or 
. a line that begins with "diff -", or 
. a line that begins with "Index: "
"

Or should the git filter also look for a "scissor-line" [3] to identify a
git-message?

[1] http://www.kernel.org/pub/software/scm/git/docs/git-send-email.html
[2] http://linux.die.net/man/1/git-am 
[3] http://linux.die.net/man/1/git-mailinfo 

Or are there any guaranteed under water git-markers in the mailheader?

-----Oorspronkelijk bericht-----
Van: Robert Mast [mailto:beheerder@tekenbeetziekten.nl] 
Verzonden: woensdag 30 januari 2013 18:15
Aan: 'Carl Worth'; 'Jani Nikula'; 'notmuch@notmuchmail.org'
Onderwerp: RE: Reply all - issue

Thanks for your clear explanation.

The thread-merging and breaking is in the procedure already pointed at by
Jani: (_notmuch_database_link_message() in lib/database.cc.)

Is there a quick way to recognize those git-threads by subject-syntax, or to
reliably tag them to exclude them from subject-breaking?




-----Oorspronkelijk bericht-----
Van: Carl Worth [mailto:cworth@cworth.org] 
Verzonden: dinsdag 29 januari 2013 3:48
Aan: Robert Mast; 'Jani Nikula'; notmuch@notmuchmail.org
Onderwerp: RE: Reply all - issue


Is there any existing thread-breaking? There wasn't the last time I looked
at the code closely, (but admittedly, that was a while ago).

-Carl