linux-kernel - Re: 2.6.19 -mm merge plans

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: <45121382.1090403@garzik.org>
Date:	Thu, 21 Sep 2006 00:22:26 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Andrew Morton <akpm@...l.org>
CC:	linux-kernel@...r.kernel.org, Linus Torvalds <torvalds@...l.org>
Subject: Re: 2.6.19 -mm merge plans

Andrew Morton wrote:
> A wander through the -mm patch queue, along with some commentary on my
> intentions.
> 
> 
> When replying to this email, please rewrite the Subject: to something
> appropriate.  Please also attempt to cc the appropriate developer(s).
> 
> 
> There are quite a lot of patches here which belong in subsystem trees. 
> I'll patchbomb the relevant maintainers soon.  Could I pleeeeeze ask that
> they either merge the patches or solidly nack them (with reasons)?  Don't
> just ignore it all and leave me hanging onto this stuff for ever.  Thanks.

I know this is probably heresy, but what would happen if we didn't merge 
all that stuff at once, and then committed to having a real 4-week cycle?

The cycles seem to be stretching out again, and I don't really think 
it's worth it to hold up the entire kernel for every single piddly 
little regression to get fixed.  We'll _never_ be perfect, even if we 
weren't slackers.

	Jeff


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