lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070430151938.66670@gmx.net>
Date:	Mon, 30 Apr 2007 17:19:38 +0200
From:	"Uwe Bugla" <uwe.bugla@....de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	hermann-pitton@...or.de, mkruky@...uxtv.org,
	akpm@...ux-foundation.org, linux-dvb@...uxtv.org,
	linux-kernel@...r.kernel.org, mrechberger@...il.com
Subject: Re: [linux-dvb] Re: Critical points about kernel 2.6.21 and
 pseudo-authorities


-------- Original-Nachricht --------
Datum: Mon, 30 Apr 2007 07:49:52 -0700 (PDT)
Von: Linus Torvalds <torvalds@...ux-foundation.org>
An: Uwe Bugla <uwe.bugla@....de>
CC: Markus Rechberger <mrechberger@...il.com>, linux-kernel@...r.kernel.org, linux-dvb@...uxtv.org, akpm@...ux-foundation.org, mkruky@...uxtv.org, hermann-pitton@...or.de
Betreff: Re: [linux-dvb] Re: Critical points about kernel 2.6.21 and pseudo-authorities

> 
> 
> On Mon, 30 Apr 2007, Uwe Bugla wrote:
> > 
> > So please Linus - rip that crap out of 2.6.21-git2. And if you do see
> questions what parts you need to rip out, please feel free to ask me....
> > 
> 
> Uwe. I'll say this ONCE more.
> 
> No.

Sorry! Sigh! Very utmost bad decision, but I must respect it.
The accumulative principle is the opposite of effectiveness.
Even if you do not understand the dvb issues in git2 (well I cannot expect this, can I?), you push

a. immature code
b. a regression

Isn't it a pity that the "maintainer" title has more influence than any kind of
common sense, reason or sophisticated argumentation?
What a horrible thought!

P. S.: In former kernel releases the specific last release candidate was almost identical to the official kernel release.

Not only I have largest problems to understand why this wonderful principle has been broken, with the effect, that the so-called "stable" kernel releases are unusable in the end.
2.6.20, 2.6.21, 2.6.19, and may be former ones that I do not know about.

A "Final" release should be "round", but never in this life highly incomplete, shouldn't it??

> 
> And unless you can become politer and more respectful and stop ranting all
> the time, you'll be in the very rare situation of hitting my auto-filters 
> and going into an email mbox of your own (read: one that I read in my 
> copious spare time. Hint: I don't _have_ any.)
> 
> 		Linus

Poor Linus!
I have got thousands of good reasons to be so rude towards some people. And I certainly know the smart polite way of the game too. I know both ways of dealing with. But if someone continues to nerve me for such a long time (whoever the specified person may be) I get out the big stick and then there will be bambule pure!

Excuse me, you are only finnish origin: "Bambule" is an invention of Ulrike Meinhof and other 68ers and stands for "revolt" or something similar.

BTW:
Wasn't it you yourself stating that if one wants changes it is not always useful to be polite??

"If you want to change something, it's not fine to be entirely polite all the time:"

(Linus Torvalds, March 6, 2007, 09:57:34, public Email).

Happy reflection, Mister Torvalds!

Uwe

-- 
"Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ