From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 783051381F3 for ; Mon, 1 Jul 2013 21:55:41 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AC9A2E0B9A; Mon, 1 Jul 2013 21:55:30 +0000 (UTC) Received: from georges.telenet-ops.be (georges.telenet-ops.be [195.130.137.68]) by pigeon.gentoo.org (Postfix) with ESMTP id 815F7E0B99 for ; Mon, 1 Jul 2013 21:55:29 +0000 (UTC) Received: from TOMWIJ-GENTOO ([94.226.55.127]) by georges.telenet-ops.be with bizsmtp id v9vU1l00K2khLEN069vUcn; Mon, 01 Jul 2013 23:55:28 +0200 Date: Mon, 1 Jul 2013 23:55:23 +0200 From: Tom Wijsman To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: [gentoo-kernel] Proper distribution integration of kernel *-sources, patches and configuration. Message-ID: <20130701235523.58018cb3@TOMWIJ-GENTOO> In-Reply-To: <20130701212454.GA32077@kroah.com> References: <20130701164149.131490f8@TOMWIJ-GENTOO> <20130701181749.GA3831@kroah.com> <20130701204516.6151bb40@TOMWIJ-GENTOO> <20130701192324.GA30808@kroah.com> <51D1F1D3.8030402@gentoo.org> <20130701212454.GA32077@kroah.com> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.19; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/7OagZ7jSdhzD=f04mO_sJ78"; protocol="application/pgp-signature" X-Archives-Salt: 0971f544-6b7f-41eb-ad4a-610bf8154592 X-Archives-Hash: 468f1288d29f2efb689de3a66adcccd5 --Sig_/7OagZ7jSdhzD=f04mO_sJ78 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 1 Jul 2013 14:24:54 -0700 Greg KH wrote: > > but suppose people > > want BFQ? Why can't we have it in gentoo-sources. It is totally > > disabled by not selecting CONFIG_BFQ. Selecting it is no different > > than emerging pf-sources with the same other options ported over. >=20 > Until you run into a patch that modifies code outside of it's CONFIG_ > option, like the aufs example I pointed out. It would be policy to not add such patches, unless wrapped with config checks by a script; further more, I discussed USE=3D-experimental with mpagano and he found this separation a good idea, we can split this into a third experimental tarball to not surprise non-Gentoo users as well. mpagano as well as I stand completely behind that gentoo-sources must remain usable for production servers; which this USE flag fulfills, as well as separate from all of this to use live ebuilds in our testing to avoid surprises that even our non-experimental genpatches could bring. (For those in #gentoo-kernel, that conversation happened there) --=20 With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : TomWij@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D --Sig_/7OagZ7jSdhzD=f04mO_sJ78 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iQEcBAEBAgAGBQJR0frOAAoJEJWyH81tNOV9y1UH/0diVaG3hG0mTHGGc8su9os8 YhSpL6DUOC+4ru8lGCiOCA0ahEc0ORi6N8PIlIn5hbD4XSnSvf5OlqHuGo/Z83I0 nDLZY8jfouo2BCPbVQqeBcXG4KGEAq3nyXOVCah5k6Fsh1lICdG1e6EhSIdCMCwE 0OnWWoppNjbZzx/DShTLBP77OKBI+T3iqQlPNxT7zod0kDBPwbxDpWIlvV5inATb uJ9ek36tip0xz4erUUatvG2wW2v5Xp97TLcjaI5dzvQ0jN0c0gt8MOaJr3Kv4Snh Gfd3l67vIzLn2s44uIvXl8TXY7nwg7tvGZWA6raRhNHKihbfQNGWoVSBXtsOiwQ= =R/2c -----END PGP SIGNATURE----- --Sig_/7OagZ7jSdhzD=f04mO_sJ78--