From: "Pedro F. «pancho» Horrillo" <phorrillo@aurigae.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] how to unlink a message from a thread?
Date: Tue, 10 Aug 2010 11:31:35 +0200 [thread overview]
Message-ID: <1281432521-sup-4463@aurigae120.hi.inet> (raw)
In-Reply-To: <1281361742-sup-3674@pinkfloyd.chass.utoronto.ca>
Excerpts from Ben Walton's message of Mon Aug 09 15:52:44 +0200 2010:
> Excerpts from Pedro F. «pancho» Horrillo's message of Mon Aug 09 06:35:01 -0400 2010:
>
> > Is there a way to 'free' a message from a thread?
>
> Lucky for you, forced thread joins aren't preserved across restarts of
> sup...unless this has changed and I didn't notice? (It's not a
> feature I use, so that is possible.)
>
Oh, I just checked to be sure, and definitely the link remains.
> Out of curiosity, where do people find the most use for this feature?
> I have a few people out there using braindead mail clients that don't
> preserve enough headers when replying that they end up starting a new
> thread in sup...I might use the thread join if it were persisted.
>
I use it to join mails that naturally belong in the same “conversation”,
even though they were not posted as actual replies to a given email.
This happens here quite often.
> The other feature that would be really cool is to split a thread. I
> interact with several people that will start a new email conversation
> by opening an old message, changing subject (and maybe recipients) and
> then sending it. This preserves the old headers, which sees sup
> append the now disjoint new topic to the old thread.
>
Same here.
> Thanks
> -Ben
>
Cheers,
--
Pedro F. «pancho» Horrillo
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2010-08-10 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 10:35 Pedro F. «pancho» Horrillo
2010-08-09 13:52 ` Ben Walton
2010-08-09 15:38 ` Erik Quaeghebeur
2010-08-10 9:31 ` Pedro F. «pancho» Horrillo [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=1281432521-sup-4463@aurigae120.hi.inet \
--to=phorrillo@aurigae.com \
--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