linux-kernel - Re: linux-next: Tree for July 14

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: <20080714101242.ace33488.akpm@linux-foundation.org>
Date:	Mon, 14 Jul 2008 10:12:42 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for July 14

On Mon, 14 Jul 2008 20:12:49 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> With the opening of the merge window, I am hoping my job becomes easier
> again ... :-)

If past experience is a guide, it's about to get harder because

a) maintainers jam untested crap^W^Wrecently-received features into
   their trees so they don't miss the merge window and

b) a storm of git rejects turn up as Linus's tree starts to get changed.

Hopefully b) will improve, as "all" the new code has already gone
through linux-next merging.

As for a), well, it would be nice if people were to be careful about
that sort of thing.  In some ways it's justifiable - we _do_ have a
couple months to fix remaining glitches.  But one would think that when
fast-tracking new features, the code would at least get additional
review and testing to make up for it.
--
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/