linux-kernel - Re: If you want me to quit I will quit

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]

Date:	Sat, 26 Apr 2008 12:18:34 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
cc:	Adrian Bunk <bunk@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Harvey Harrison <harvey.harrison@...il.com>,
	Mauro Carvalho Chehab <mchehab@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: If you want me to quit I will quit

On Sat, 26 Apr 2008, Linus Torvalds wrote:
> 
> So:
>  - making things public is *different* from developing them. Don't push 
>    out just because you committed something!
> 
>  - you shouldn't publicize a tree until it's in reasonable shape. EVER. 
>    Even -mm or -next is *not* better off with a pile of sh*t just because 
>    you're working in that area. 
> 
>    I cannot stress this enough. I think Andrew has been way too polite to 
>    some people.
> 
>  - and once it is, you generally shouldn't mess with old commits even when 
>    you fix things. Full cleanliness or always being able to bisect 
>    specific configurations is not an excuse for messing up all the other 
>    things, and if this problem happens a lot, I would like to point you to 
>    the two previous points.

And btw, a *big* part of the above is also:

 - mistakes happen.

There will be bugs. There will be cases where things aren't bisectable 
(although they should generally be bisectable for *your* configuration, 
because if they aren't, that shows that you didn't even compile the 
commits you made).

And there will be kernels that don't boot. Even expecting people to always 
boot-test every single commit would be unrealistic - let's face it, most 
things look really obvious, and the fact that even obvious fixes can have 
bugs doesn't mean that there should be hard rules about "every single 
commit has to be boot-tested on X machines".

So it's an important part of the process to try to do a good job, and not 
publicizing crap - but it's *equally* important to realize that crap 
happens, and that it's easily *more* distracting to try to clean it up 
after-the-fact than it is to just admit that it happened.

		Linus
--
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/