| 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
| ||
|
Message-Id: <20081118084757.5c92c878.randy.dunlap@oracle.com> Date: Tue, 18 Nov 2008 08:47:57 -0800 From: Randy Dunlap <randy.dunlap@...cle.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>, Linus <torvalds@...ux-foundation.org> Subject: Re: linux-next: procedures On Wed, 12 Nov 2008 17:38:07 +1100 Stephen Rothwell wrote: ... > The following will cause a tree to be temporarily dropped from linux-next: > - non-trivial conflicts with Linus' tree > - build failures Hi Stephen, One clarification, please. Does this mean build failures that _you_ see/experience during tree merging and not other reported build failures? Thanks, ~Randy > - non-obvious conflicts with other trees (this will require > us to come up with some way forward for the trees involved) > - the contact for the tree being unresponsive > > Most conflicts will be notified to the contacts for the trees involved > (some really trivial ones will not). Simple conflicts between trees I > will try to fix up (if possible) and carry such resolutions as necessary. > > I will not, any more, carry fix up patches to make linux-next build or > boot. If a tree is identified as causing such a problem, it will be > dropped until the problem is fixed. > > This is all open to discussion ... -- 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/
Powered by blists - more mailing lists