Reply all - issue

[Robert Mast]

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 at tekenbeetziekten.nl] 
Verzonden: woensdag 30 januari 2013 18:15
Aan: 'Carl Worth'; 'Jani Nikula'; 'notmuch at 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 at cworth.org] 
Verzonden: dinsdag 29 januari 2013 3:48
Aan: Robert Mast; 'Jani Nikula'; notmuch at 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