Wow, I have been on the internet since 1986, and I had never realized that this could be a problem. I am often guilty of the same, for lazyness reasons, as this is a convenient way to avoid having to reenter the "to", "cc", and "bcc" fields.
I went back to James' original message, which my mail client definitely does NOT show as a followup to anything. But when I examine its raw headers, I found this one: In-reply-to: <b537e3a60907011151q563194e5g184c8f2cbd68d...@mail.gmail.com> Is this the header that made you point your finger? In any case, I learned something today, and though this is off-topic here, it may be worth going to the bottom of this. Jean-Denis On 7/1/09 22:41 , "P Kishor" <punk.k...@gmail.com> wrote: > On Wed, Jul 1, 2009 at 3:39 PM, James Gregurich<bayouben...@mac.com> wrote: >> >> How would I have "hijacked" a thread? I changed the subject and >> removed the original text. >> > ... > > that is exactly how a thread is hijacked... changing the subject is > not enough. Every message has a unique id that is used by the mail > programs to keep track of threading. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
