Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
* [sup-talk] forwarded messages
@ 2008-03-13 16:06 John Bent
  2008-03-14 18:40 ` William Morgan
  0 siblings, 1 reply; 2+ messages in thread
From: John Bent @ 2008-03-13 16:06 UTC (permalink / raw)


Whenever I forward a message, it appears as a new thread.  I always then tag
it and the original and merge them.  Is there a way to make this happen
automagically?  Should that rather be the default behavior?

Thanks,

John


^ permalink raw reply	[flat|nested] 2+ messages in thread

* [sup-talk] forwarded messages
  2008-03-13 16:06 [sup-talk] forwarded messages John Bent
@ 2008-03-14 18:40 ` William Morgan
  0 siblings, 0 replies; 2+ messages in thread
From: William Morgan @ 2008-03-14 18:40 UTC (permalink / raw)


Reformatted excerpts from John Bent's message of 2008-03-13:
> Whenever I forward a message, it appears as a new thread.  I always
> then tag it and the original and merge them.  Is there a way to make
> this happen automagically?  Should that rather be the default
> behavior?

I've thought about having this be the default behavior because I often
do that as well. There are two ways it could go: actually add a
References: header (or a in-reply-to?), which would be pretty
nonstandard, I think, or just do it in the index itself.

The dirty secret of the thread joining (which I've just realized now) is
that the joins won't be preserved if you reindex those messages. I need
to add another blob of information somewhere to preserve that stuff.  If
I added the header to the outgoing message, the threading would be
preserved, of course...

-- 
William <wmorgan-sup at masanjin.net>


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2008-03-14 18:40 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-03-13 16:06 [sup-talk] forwarded messages John Bent
2008-03-14 18:40 ` William Morgan

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox