Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] how to unlink a message from a thread?
Date: Mon, 09 Aug 2010 09:52:44 -0400	[thread overview]
Message-ID: <1281361742-sup-3674@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <1281349768-sup-7718@aurigae120.hi.inet>

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.)

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.

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.

Thanks
-Ben

--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

  reply	other threads:[~2010-08-09 14:11 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 [this message]
2010-08-09 15:38   ` Erik Quaeghebeur
2010-08-10  9:31   ` Pedro F. «pancho» Horrillo

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=1281361742-sup-3674@pinkfloyd.chass.utoronto.ca \
    --to=bwalton@artsci.utoronto.ca \
    --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