On Mon, 1 Jul 2013 14:09:57 -0500 Matthew Summers <quantumsumm...@gentoo.org> wrote:
> I think the point was well-made by grehkh. You missed my response to that point. > If the patchset patches the kernel's core, it doesn't matter what > CONFIG_* option is set the core kernel code _has_now_been_changed_. > This is the crux of the argument, I believe. AUFS simply being one > example of this. I'm sure there are others. As per my response to that point, this statement is no longer true. Let me re-iterate it here: Earlier I mentioned "3) The patch should not affect the build by default."; if it does, we have to adjust it to not do that, this is something that can be easily scripted. It's just a matter of embedding each + block in the diff with a config check and updating the counts. -- With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : tom...@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
signature.asc
Description: PGP signature
