linux-kernel - Re: [PATCH 0/90] Post 2.6.21 OMAP update

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 4 Apr 2007 22:44:48 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Tony Lindgren <tony@...mide.com>
Cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/90] Post 2.6.21 OMAP update

> > That's only a problem when there are <too many> patches to be
> > reviewed.  Hence, do more frequent postings of fewer patches per series.
> > That will likely also get you more reviewers.
> 
> Yeah, I agree.. We've already missed two merge windows because of the
> large patch set :( The problem is that patch set just keeps growing.

The other problem is that GIT patch sets are completely useless for
merging and reviewing if you simply fire off a blast of 70 changesets.
Each time you do it at least one gets queried or a NAK and the lot go in
the bin again. Repeat 50 times...

It would be enormously helpful if instead we got say 15 small patch sets
which are independant so that a query or NAK means 14 sets get applied
this time around not zero.

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