[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    Re: [Bug 54474] changing subject does not break thread
From:       Ingo =?iso-8859-1?q?Kl=F6cker?= <kloecker () kde ! org>
Date:       2003-02-16 12:47:17
[Download RAW message or body]

On Saturday 15 February 2003 04:36, Don Sanders wrote:
> On Saturday 15 February 2003 07:03, Ingo Klöcker wrote:
> > On Friday 14 February 2003 13:24, Bernhard Reiter wrote:
> > > On Thursday 13 February 2003 01:31, Ingo Klöcker wrote:
> > > > On Wednesday 12 February 2003 04:56, Don Sanders wrote:
> > > > > Maybe a possible compromise.
> > > > >
> > > > > If the subject has been changed and stripped of all reply
> > > > > prefixes
> > > >
> > > > and if the "reply" doesn't contain any quoted text
> > > >
> > > > > then the thread is broken.
> > > >
> > > > I think if all of the aforementioned conditions are met then we
> > > > can safely assume that the "reply" is actually the start of a
> > > > new thread.
> > >
> > > I tend to disagree.
> > > AFAIK there were quite some discussions about this when I still
> > > read the newsgroups about newsreaders
> > > where the same question is even more important.
> > >
> > > A subject can be changed often in a threat especially
> > > when it splits into subthreads.
> >
> > Granted. But wouldn't a reply include at least some quoted text
> > (even if it's a new subthread)?
>
> This is an entirely independent subject. I'm intending to work on
> threading of received messages.
>
> Threading of composed messages is a valid topic to discuss, but it's
> a separate topic from threading of received messages.

Actually I thought we were talking about the generation of In-reply-to 
and References headers for composed replies and not about threading 
received messages. It seems I misunderstood the original wish.

Regards,
Ingo


[Attachment #3 (application/pgp-signature)]
_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail

[prev in list] [next in list] [prev in thread] [next in thread]