[syslinux] mixed email threads

[Gene Cumm]

On Mon, Feb 29, 2016 at 3:49 PM, Ryan Novosielski via Syslinux
<syslinux at zytor.com> wrote:
> On Mon, Feb 29, 2016 at 08:28:47PM +0000, Patrick Masotta wrote:
>> On Mon, Feb 29, 2016 at 10:15:10PM +0200, Ady wrote:
>> >
>> > Your first email about your efi/udp.c patch seems to be part of another
>> > email thread, and not a separate email thread as it was supposed to be.
>> >
>> > See
>> > http://www.syslinux.org/archives/2016-February/thread.html#24866
>> >
>> > and scroll up.
>> >
>>
>> I see it now,
>> well I have no idea why that happen
>> As you said, I might've taken an e-mail from the list and
>> replied erasing the old text; probably some unseen
>>
>> left over made the mistake. Sorry.
>
> This is basically the only reason that this happens, and is something
> that most people learn not to do the hard way (myself included). Rule of
> thumb: if you are writing to a mailing list, compose a new/blank e-mail
> to the list address.
> If you click reply, and aren't sure what you're doing, you'll end up
> screwing up threading for other people that use threaded e-mail readers,
> including Thunderbird and others that don't care if the "Subject:"
> header changes, but stick to the "In-Reply-To:" header. This sort of
> thing falls under thread-hijacking, though it's a lot more subtle example.

It's also a per-client difference.  In example, GMail's web client and
Android App did not group those messages to one conversation.  It
commonly forces a break when a subject diverges more than say "Re: "

-- 
-Gene