-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2007-11-24 a las 18:26 -0500, Ruben Safir escribió:
Message-ID: <20071123180019.GA18713@www2.mrbrklyn.com> References: <1195816660.30586.54.camel@g168.suse.de> <1195840395.5152.43.camel@desktop.bryen.info> In-Reply-To: <1195840395.5152.43.camel@desktop.bryen.info>
You see that you are in fact answering to an email from Bryen, replacing the subject line with another:
Message-Id: <1195840395.5152.43.camel@desktop.bryen.info>
That's a full blown intentional thread hijack.
You spend too much time examing headers and finding ways to insult people.
Me? Insulting you? Where do you get that impression? :-O Everybody here is witness I did not.
But for what it is worth, it was easier to reply to a random message and to change the subject then to try to copy and paste the email address from from the list through vnc on a windows box at work through a web browser.
That's precisely a thread hijack. You confessed!
It might occur to you that a threadinging implementation (one which is not BTW part of mutt on SuSE) that can't figure out that the subject line has changed is by definition a broken implementation.
The subject line change is irrelevant for threading, and thus, ignored.
But do me and the entire list a favor. Next time you decide to rant with little or no provocation, by all means, use your procmail to dev null me and save everyone bandwidth. I've used the same email address for about 7 years so this shouldn't be so hard.
In the mean time ask yourself if it is easier to flail away helplessly at winmills and trying to get everyone on earth to conform to a misguild sense of universal justice, or to exert self control on your individual behavior.
In the mean time, I've been apreciative of the help I've recieved here, less enthrawed with the rudeness. But this is par for a list as large as this one. There are aways a lot of ego's floating around with a list this large and with this much traffic.
As always
Resectfully yours
- -- Saludos Carlos E.R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFHSMAmtTMYHG2NR9URArbjAJ4uUcxOwZj4G4uFvOE/AF6d9VV2bQCfb0DY rnnW+lSt3sj6mUDS0UaOGMM= =8JKl -----END PGP SIGNATURE-----