From: "Robert Mast" <beheerder@tekenbeetziekten.nl>
To: "'Carl Worth'" <cworth@cworth.org>,
"'Jani Nikula'" <jani@nikula.org>, <notmuch@notmuchmail.org>
Subject: RE: Reply all - issue
Date: Wed, 30 Jan 2013 18:14:48 +0100 [thread overview]
Message-ID: <00bf01cdff0d$4ecedd10$ec6c9730$@nl> (raw)
In-Reply-To: <87boc8bt8a.fsf@yoom.home.cworth.org>
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
next prev parent reply other threads:[~2013-01-30 17:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 21:58 Reply all - issue Robert Mast
2013-01-28 15:13 ` Jani Nikula
2013-01-28 18:15 ` Robert Mast
2013-01-29 2:47 ` Carl Worth
2013-01-30 17:14 ` Robert Mast [this message]
2013-01-30 21:39 ` Suvayu Ali
2013-01-31 10:21 ` Andrei POPESCU
2013-01-30 20:56 ` Robert Mast
2013-01-30 21:49 ` Robert Mast
2013-01-31 1:12 ` David Bremner
2013-01-31 1:14 ` David Bremner
2013-02-12 7:07 ` Jameson Graef Rollins
2013-02-12 19:17 ` Carl Worth
2013-01-31 10:52 ` Michał Nazarewicz
2013-02-02 16:21 ` Robert Mast
2013-02-02 20:52 ` David Bremner
2013-02-03 0:06 ` [Spam-verdenking][english 100%] " Robert Mast
2013-02-03 15:26 ` Robert Mast
2013-02-03 18:28 ` David Bremner
2013-02-10 15:43 ` Robert Mast
2013-02-04 10:39 ` Michał Nazarewicz
2013-02-04 15:29 ` Suvayu Ali
2013-02-06 18:19 ` Istvan Marko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00bf01cdff0d$4ecedd10$ec6c9730$@nl' \
--to=beheerder@tekenbeetziekten.nl \
--cc=cworth@cworth.org \
--cc=jani@nikula.org \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).