linux-kernel - Re: linux-next: please hold off 2.6.28 stuff

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: <1216620821.13328.14.camel@brick>
Date:	Sun, 20 Jul 2008 23:13:41 -0700
From:	Harvey Harrison <harvey.harrison@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: linux-next: please hold off 2.6.28 stuff

On Mon, 2008-07-21 at 13:51 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Andrew mentioned this and I just thought I would reinforce the message:
> 
> Please do not put 2.6.28 code into linux-next until at least after -rc1.
> This will help Andrew's sanity :-)

I would say let -rc2 be the flag for putting things for the next (2.6.28) release
into -next.  That would give akpm time to get his load in as well.
Between -rc1 and -rc2, he could look at -next to see what patches were
picked up by maintainers and what he'll still have to send in himself.

But it's not me doing the work :-)

Keep up the good work Stephen/AKPM.

Harvey

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