From: Tero Tilus <tero@tilus.net>
To: Sup users <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Add messages to a thread manually
Date: Sun, 20 Nov 2011 00:26:04 +0200 [thread overview]
Message-ID: <1321740372-sup-1779@tilus.net> (raw)
In-Reply-To: <1321738838-sup-4532@masterkorp.net>
Alfredo Palhares, 2011-11-19 23:48:
> Is there a way for me to manually add a message to a thread?
Tag messages in thread index mode and hit # (Force tagged threads to
be joined into the same thread). Back when I needed that
functionality more I had a bit flaky feeling about it. It randomly
just wouldn't work. Dunno how it is now. Haven't really used it.
> Also a way of threating this in the before-add-message hook would be
> very cool.
At some point I played with the idea a bit. Most of the time if you
get a reply without refs from a particular address, all the other
mails from that address will be refs-free too. Also the refs-free
repliers tend to be top-posters. And replies usually are received
within relatively short time after the original. Ideally you should
be able to take advantage of those and be able to rebuild refs
relatively accurately.
Once you manually build an in-reply-to ref, automatic detector would
know to regard that sender as a usual suspect. In addition to the
subject, you could also use the body of the top-post reply to
automatically find out the source of the quote.
--
Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-11-19 23:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 21:48 Alfredo Palhares
2011-11-19 22:26 ` Tero Tilus [this message]
2011-11-21 14:38 ` Сергей Z
2011-11-21 17:07 ` Tero Tilus
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=1321740372-sup-1779@tilus.net \
--to=tero@tilus.net \
--cc=sup-talk@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox