linux-kernel - Re: Announce: Linux-next (Or Andrew's dream :-))

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: <20080212210808.GJ27894@ZenIV.linux.org.uk>
Date:	Tue, 12 Feb 2008 21:08:08 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Greg KH <greg@...ah.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Jeff Garzik <jeff@...zik.org>,
	David Miller <davem@...emloft.net>, arjan@...radead.org,
	sfr@...b.auug.org.au, linux-kernel@...r.kernel.org,
	linux-next@...r.kernel.org, linux-arch@...r.kernel.org,
	akpm@...ux-foundation.org
Subject: Re: Announce: Linux-next (Or Andrew's dream :-))

On Tue, Feb 12, 2008 at 12:50:51PM -0800, Greg KH wrote:

> I can run the numbers, but almost every one of those changes has at
> least 2 signed-off-by: on them, so they should all be being reviewed
> properly.
> 
> > AFAICS, we are in situation when review bandwidth is where the bottleneck
> > is.  Not the merge one...
> 
> Are there still large numbers of posted patches, not reviewed or picked
> up by anyone laying around somewhere?  I thought Andrew-the-patch-vacuum
> had been doing a great job of keeping that from happening lately.

Er...  Surely you can think of examples of patches that went through
-mm without serious review?  Not to mention that 2 S-o-B normally
means only one thing: "went to Linus through some tree".  Which does
not guarantee any real review, as you damn well know.
--
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/