linux-kernel - Re: Slow DOWN, please!!!

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:	Thu, 1 May 2008 16:06:59 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	David Miller <davem@...emloft.net>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jiri Slaby <jirislaby@...il.com>
Subject: Re: Slow DOWN, please!!!

On Thursday, 1 of May 2008, Stefan Richter wrote:
> Rafael J. Wysocki wrote:
> > And what do you think is happening _after_ the merge window closes, when
> > we're supposed to be fixing bugs?  People work on new code.
> 
> That's not correct.  People work on new code before, during, and after 
> the merge window.  They also fix bugs before, during, and after it.

I'm not quite sure if really all of them do.  Well, I should have said "some
people" instead of just "poeple" to be fair.

> > And, in fact, they have to, if they want to be ready for the next merge
> > window.
> 
> To be ready for the next merge window just means to know which code is 
> sufficiently reviewed and tested, and to have it queued up and if 
> necessary synchronized with other pending code.

Of course it _should_ mean that, but the fact is unreviewed and untested
patches are pushed to Linus, at least from time to time.  [Even some known
broken patches were pushed to Linus in the past, but we can't prevent that from
happening by any process changes.]

Thanks,
Rafael
--
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/