-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LSU.2.11.1406280355040.5367@Telcontar.valinor> On Friday, 2014-06-27 at 05:05 -0700, Bruce Ferrell wrote:
On 06/27/2014 04:58 AM, C wrote:
On Fri, Jun 27, 2014 at 1:52 PM, Bruce Ferrell <> wrote:
...
Please take a look in the mail archives starting here: http://lists.opensuse.org/opensuse/2014-06/threads7.html You can see the post you started that broke the threading.. it stands alone as the break point.
Then look back one page to see the result of the thread hijacking http://lists.opensuse.org/opensuse/2014-06/threads6.html all of the replies end up interleaved into the thread that was hijacked.
A simple poke at the archives shows immediately what the effects of thread hijacking are.
C. the full source of the original post:
From - Sun Jun 22 13:40:55 2014 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00800000 X-Mozilla-Keys: Message-ID: <53A73F57.7010803@baywinds.org> Date: Sun, 22 Jun 2014 13:40:55 -0700 From: Bruce Ferrell <bferrell@baywinds.org> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: OS-EN <opensuse@opensuse.org> Subject: Asus G750JW wifi (Broadcom BCM4352) and kernel 3.15 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit
But Bruce, Patrick did not say you hijacked the thread, but Rainer Klier. Your reaction was excessive, because indeed there was a thread hijack, although you did not do it. You should have noticed it, though, as it is against the openSUSE Mailing list netiquette, and perhaps you could have done something, like adding a note about it on the mail (asking for excuses, preventing the possible reaction), or answering on the correct thread instead, or warning Rainer of the problem. You have been around here for a decade at least, so you should know that. His post contains these headers: +++······························ Organization: xyzmo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 Content-class: urn:content-classes:message Subject: Re: [opensuse] Asus G750JW wifi (Broadcom BCM4352) and kernel 3.15 Date: Mon, 23 Jun 2014 13:59:30 +0200 Message-ID: <CCB7BB9A084B54488017902E52BBE3A502C06073@TSEXCHANGE.trosoft.local> In-Reply-To: <CAOVv=gOSfXgr=WV57BfEhBX2TOoHD01kUKqxv00B=r4SbD6Nmg@mail.gmail.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [opensuse] Asus G750JW wifi (Broadcom BCM4352) and kernel 3.15 Thread-Index: Ac+O2pdYFLMZTG+XRGChv6lw3IYb+g== References: <CAOVv=gOSfXgr=WV57BfEhBX2TOoHD01kUKqxv00B=r4SbD6Nmg@mail.gmail.com> From: "Rainer Klier" <...@xyzmo.com> To: <opensuse@opensuse.org> ······························++- You see, both the "In-Reply-To" and "References" headers point to this other post as parent: +++······························ From: C <...@opensuse.org> Date: Sat, 21 Jun 2014 22:18:57 +0200 Message-ID: <CAOVv=gOSfXgr=WV57BfEhBX2TOoHD01kUKqxv00B=r4SbD6Nmg@mail.gmail.com> Subject: [opensuse] The "right" way to clear up /tmp? To: openSUSE <opensuse@opensuse.org> ······························++- So it is apparent that Rainer Klier mail tool chain is the culprit. He is using the same Thunderbird version you have, but there are a few suspicious headers: +++······························ X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [opensuse] [opensuse] Asus G750JW wifi (Broadcom BCM4352) and kernel 3.15 Thread-Index: Ac+OuWvlfbAj/qsNQKq5WSgnx9i4+A== ······························++- which make me suspect there is a Windows mail server involved, perhaps with a broken indexer. Dunno, but he has to investigate it, because it causes havoc. - -- Cheers, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlOuIMUACgkQtTMYHG2NR9WVVwCfWMw0STlNOxMO492YrJ+6Uo3N kycAn3NMv3hey5uitU4Ur7JG3JCuKGJD =xr+q -----END PGP SIGNATURE-----