On Wed, 3 Jul 2013 22:00:19 -0400
Walter Dnes waltd...@waltdnes.org wrote:
Here's my user, not-a-developer, perspective. I think that there
should be a mechanism to enable one patch at a time. Here's the
rationale...
Haven't tried this myself but I believe UNIPATCH_EXCLUDE using
the
Tom Wijsman wrote:
Greg KH wrote:
On Mon, Jul 01, 2013 at 09:25:42PM +0200, Tom Wijsman wrote:
On Mon, 1 Jul 2013 14:09:57 -0500
Matthew Summers quantumsumm...@gentoo.org wrote:
If the patchset patches the kernel's core, it doesn't matter what
CONFIG_* option is set the core
On Wed, 3 Jul 2013 11:45:55 +0100
Steven J. Long sl...@rathaus.eclipse.co.uk wrote:
Tom Wijsman wrote:
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.
If it
On Wed, Jul 03, 2013 at 02:42:56PM +0200, Tom Wijsman wrote
With USE=-experimental (which will be the default) they are excluded by
default, after enabling that the user can exclude patches by setting
UNIPATCH_EXCLUDE through the package.env mechanism.
Here's my user, not-a-developer,
