| 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
| ||
|
Date: Thu, 11 Jun 2015 06:31:31 +1000 From: Neil Brown <neilb@...e.de> To: David Teigland <teigland@...hat.com> Cc: Goldwyn Rodrigues <rgoldwyn@...e.com>, linux-kernel@...r.kernel.org Subject: Re: clustered MD On Wed, 10 Jun 2015 10:01:51 -0500 David Teigland <teigland@...hat.com> wrote: > Isn't this process what staging is for? No it isn't. Staging is useful for code drops. i.e. multiple other developers want to collaborate to improve some code that the maintainer doesn't want to accept. So it goes into staging, "the community" gets a chance to use the kernel development workflow to fix it up, and then it either is accepted by the maintainer, or is eventually discarded. cluster-MD has followed a very different process. The relevant maintainer (me) has been involved from the start, has provided input to the design, and reviewed various initial implementations, and now thinks that the code is close enough to ready for it to be included in the kernel (with suitable warnings). That way I only need to review incremental changes, not the whole set of patches from scratch each time. What is your interest in this? I'm always happy for open discussion and varied input, but it would help to know to what extent you are a stake holder? Also a slightly less adversarial tone would make me feel more comfortable, though maybe I'm misreading your intent. Thanks, NeilBrown -- 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