From: kashani <kashani-list@badapple.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Don't start a new thread by changing the subject
Date: Fri, 24 Jun 2011 17:43:31 -0700 [thread overview]
Message-ID: <4E052F33.70109@badapple.net> (raw)
In-Reply-To: <20110625010931.73bd42d0@karnak.local>
On 6/24/2011 5:09 PM, David W Noon wrote:
> On Fri, 24 Jun 2011 16:12:26 -0700, kashani wrote about [gentoo-user]
> Don't start a new thread by changing the subject:
>
>> I've noticed this a couple of times this week. A few of you
>> have responded to the annoying Fortran thread, changed the subject,
>> started a new message, and sent the email starting a new thread.
>
> You're a week or two behind the times. The root cause of this was done
> to death some time ago. It is the bofh.it NNTP server that propagates
> this mailing list through Usenet. There is nothing we can do except
> avoid using servers downstream from that rogue server.
My understanding is that the NNTP server was munging headers thereby
creating new threads where it should have been a single thread. This is
users responding to an existing email, removing all content, changing
the subject, and then sending the mail which keeps the thread headers
and make it appear to be part of the current thread. I see it all the
time on the motorcycle lists where the average user is much less
computer proficient.
kashani
next prev parent reply other threads:[~2011-06-25 0:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 23:12 [gentoo-user] Don't start a new thread by changing the subject kashani
2011-06-25 0:09 ` David W Noon
2011-06-25 0:43 ` kashani [this message]
2011-06-25 3:31 ` Dale
2011-06-25 12:25 ` David W Noon
2011-06-25 11:47 ` Volker Armin Hemmann
2011-06-25 18:32 ` Alan McKinnon
2011-06-25 19:27 ` Alan Mackenzie
2011-06-25 8:09 ` Marc Joliet
2011-06-25 10:39 ` enno+gentoo
2011-06-25 12:13 ` methylherd
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=4E052F33.70109@badapple.net \
--to=kashani-list@badapple.net \
--cc=gentoo-user@lists.gentoo.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