linux-kernel - Re: HTC Dream aka. t-mobile g1 support

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, 11 Jun 2009 15:21:17 +0200
From:	Pavel Machek <pavel@....cz>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	David Miller <davem@...emloft.net>, swetland@...gle.com,
	linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.arm.linux.org.uk, san@...roid.com,
	rlove@...gle.com
Subject: Re: HTC Dream aka. t-mobile g1 support

On Thu 2009-06-11 13:38:52, Russell King - ARM Linux wrote:
> On Thu, Jun 11, 2009 at 05:00:30AM -0700, David Miller wrote:
> > From: Russell King - ARM Linux <linux@....linux.org.uk>
> > Date: Thu, 11 Jun 2009 12:49:12 +0100
> > 
> > > I can not keep up with the number of patches that need to be
> > > reviewed and ultimately merged.  I know this, and I freely admit it,
> > > and I have done so on many occasions.
> > 
> > Then split up the responsibilities to other people instead of being
> > the choke point.  Controlling everything isn't so important.
> 
> Don't you think that I've been trying to get other people to be more
> involved?
> 
> - I've been pushing people to send patches to the relevent mailing
>   list(s) and maintainer(s) for years.

The patch system is actively harmful here, because you either send the
system for discussion, or for inclusion. Picking the patches from the
mailing list when there are no significant comments (as done on lkml)
seems to work better. 

> If patchwork can replace what my patch system does for me (which is
> basically to help ensure that patches don't get lost which need
> applying - that's different from logging every single patch) then
> I'll gladly look at it.  It will mean that some of the sanity checks
> on the patch content, which happen automatically with the patch system,
> will need to be done manually.
> 
> If patchwork just gathers up every patch which has ever been seen on
> a mailing list, then stuff will get lost at a higher rate than today
> and it will have a negative impact.

I believe you are concentrating on "patch loss rate" a bit too
much. lkml does have higher "patch loss rate", still it seems
better/nicer/easier to work with.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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/