unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Carl Worth <cworth@cworth.org>
To: Mark Anderson <markr.anderson@amd.com>,
	notmuch <notmuch@notmuchmail.org>
Subject: Re: Threading
Date: Thu, 10 Dec 2009 09:39:48 -0800	[thread overview]
Message-ID: <87ws0ug23f.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <1260400470-sup-5775@testarossa>

[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

On Wed, 9 Dec 2009 16:21:34 -0700, Mark Anderson <markr.anderson@amd.com> wrote:
> I was wondering if there's a way in notmuch to group un-associated
> threads into a single thread.

There's certainly nothing like that in notmuch currently.

Sup had user-level functionality in the interface for stitching messages
into a single thread, and I definitely think that that doesn't make any
sense.

> I have a bug tracking system that doesn't give me emails that thread naturally in notmuch.

I've seen similar things. Bugzilla emails at least all group into a
single thread in notmuch, but don't get nested correctly at all, and
that's really annoying.

> I wouldn't mind writing a filter that could help identify a thread id
> which should apply to a message, and suggest that to notmuch.

I think the right answer here is to fix the input that notmuch is
getting. Just ensure that each message has a proper In-Reply-To header
and all should be fine. If you can't fix the bug-tracking system to emit
proper email, can you apply your filter and rewrite the message as part
of delivery (before notmuch sees it)?

-Carl

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2009-12-10 18:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 23:21 Threading Mark Anderson
2009-12-10 17:39 ` Carl Worth [this message]
2009-12-10 19:08   ` Threading Marten Veldthuis
2009-12-10 21:30     ` Threading Carl Worth
2009-12-15 15:54       ` Threading Marten Veldthuis
2009-12-23 22:07         ` Threading Mark Anderson
2010-01-08  3:12 ` Threading martin f krafft
2010-01-14 22:08   ` Threading Carl Worth
2010-01-14 22:37     ` Threading martin f krafft

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=87ws0ug23f.fsf@yoom.home.cworth.org \
    --to=cworth@cworth.org \
    --cc=markr.anderson@amd.com \
    --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).