linux-kernel - Re: charter for -next

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]

Message-ID: <481C6632.8070506@garzik.org>
Date:	Sat, 03 May 2008 09:18:42 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: charter for -next

Stefan Richter wrote:
> What should I ask myself before I commit something to the branch which 
> Stephen pulls into -next?
> 
>     Is this ready to be pulled by Linus right now if he had a merge
>     window open today?

I was under the impression it was the above -- anything in linux-next 
should be ready to be pulled by Linus.  The maintainer considers those 
changes "ready for next merge window."

	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/