From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Wrong messages in thread
Date: Mon, 15 Jun 2009 06:34:29 -0700 [thread overview]
Message-ID: <1245072716-sup-829@entry> (raw)
In-Reply-To: <1245027174-sup-4117@andariel>
Reformatted excerpts from Arvid Picciani's message of 2009-06-14:
> 1) Some messages end up in the wrong thread. When there is no other
> useful info, sup appears to guess a thread by the Subject similarity.
Sup does not do this. If you're seeing messages with different subjects
in the same thread, a later one contains a reference to an earlier one.
Sometimes this happens if people reply to a mailing list message and
change the subject as a way of starting a new message. You can confirm
this by examining the in-reply-to and references headers of the later
message.
> 2) how's that address book generated?
> I have sup-talk-request and sup-talk-something
> but not sup-talk.
By manually adding contacts, e.g. with 'i' in thread-view-mode, plus a
couple recent contacts automatically drawn from the index.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2009-06-15 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 0:58 Arvid Picciani
2009-06-14 17:36 ` Edward Z. Yang
2009-06-15 12:03 ` Nicolas Pouillard
2009-06-15 13:34 ` William Morgan [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1245072716-sup-829@entry \
--to=wmorgan-sup@masanjin.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox