@proxy-maintainers : Please update the tree with the attached ebuilds for the 3.6.11-r2 / 3.7.10-r1 / 3.8.3 releases. Reproducible: Always
Created attachment 342494 [details] ck-sources-3.6.11-r2.ebuild Ebuild for the 3.6.11-r2 release. Based on : - Sources for the linux 3.6 branch - genpatches rev 13 (Fixing Bug 462066) - 3.6-ck1 patchset including bfs-425
Created attachment 342496 [details] ck-sources-3.7.10-r1.ebuild Ebuild for the 3.7.10-r1 release. Based on : - Sources for the linux 3.7 branch - genpatches rev 14 (Fixing Bug 462066) - 3.7-ck1 patchset including bfs-427
Created attachment 342498 [details] ck-sources-3.8.3.ebuild Ebuild for the 3.8.3 release. Based on : - Sources for the linux 3.8 branch - genpatches rev 6 (Fixing Bug 462066) - 3.8-ck1 patchset including bfs-428 Additional Notes : a/- The upgradeable read/write locks experimental patch is not made available with this release. b/- The ck patchset no longer alters the dirty ratios default values.
just for future reference. Please use Components: Ebuilds when your bug is related to new/modified ebuilds.
(In reply to comment #4) > just for future reference. Please use Components: Ebuilds when your bug is > related to new/modified ebuilds. I usually do but forgot this time. Apologizes. While this topic is opened... 1/ I notice you recently decided to change the category from core-system (said to concern packages in sys-*) to ebuilds 2/ You change the summary which no longer starts with the package's references as I had understood being a best practice over here. I do not personally mind and as long as you are the only one taking care of my bugs, I am of course ready to conform to whatever you'll find the more efficient for you, but please tell the rules you'd like to be observed.
(In reply to comment #5) > (In reply to comment #4) > > just for future reference. Please use Components: Ebuilds when your bug is > > related to new/modified ebuilds. > I usually do but forgot this time. Apologizes. > > While this topic is opened... > > 1/ I notice you recently decided to change the category from core-system > (said to concern packages in sys-*) to ebuilds > 2/ You change the summary which no longer starts with the package's > references as I had understood being a best practice over here. > > I do not personally mind and as long as you are the only one taking care of > my bugs, I am of course ready to conform to whatever you'll find the more > efficient for you, but please tell the rules you'd like to be observed. Having such bugs prefixed with "Version bump" makes it easier for me to prioritize them in my head. as for the category, I don't know what qualifies for core-system, and since ck-sources is not an official supported kernel, it is not something that belongs there anyway. It really makes no difference. Just personal preference.
(In reply to comment #6) > Just personal preference. No problem, I will conform to this in the future. On a side note : > I don't know what qualifies > for core-system, and since ck-sources is not an official supported kernel, > it is not something that belongs there anyway. As per http://www.gentoo.org/doc/en/gentoo-kernel.xml#doc_chap2 the ck-sources are listed among the "Supported kernel packages" But... whisper it not ! (Just in case one would suddenly realize that a "supported kernel package" needs an official dev as maintainer...)
Ebuilds now in tree. Thanks