linux-kernel - 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-next>] [day] [month] [year] [list]

Date:	Sat, 03 May 2008 12:12:50 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Andrew Morton <akpm@...ux-foundation.org>
CC:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: charter for -next

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?
or
     Is it likely that I will let Linus pull this when he opens his next
     merge window?  (Assuming I can roughly predict when this will be,
     and what other work will likely be done until then, e.g. pending
     reviewer feedback, or patches for related functionality which should
     be bundled with the work in question...)
-- 
Stefan Richter
-=====-==--- -=-= ---==
http://arcgraph.de/sr/
--
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/