On Tue, 2008-05-27 at 11:58 +0300, Adrian Bunk wrote:NAK - Most if not all issues have fixes or specific reverts already. Your suggestion is really quite ridiculous and offensive to me. BROKEN is for stuff that crashes kernels or corrupts user data. Group scheduling does neither. As I've said - and which you so 'tactfully' quoted - group scheduling is a mathmatically complex topic that we are improving actively. The feature is not enabled by default and it depends on EXPERIMENTAL. Adrian - if you care about the subject so much - dive into the code and help us, instead of becoming an obstacle. These past years you've shown you're capable of understanding trivial C snippets, here is an opportunity to show you can do real stuff too. FYI your attitude in the past few weeks is getting on my nerves - you act all self important but have not made a single contribution to the kernel above the level of a janitor-newbie. --
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 007/196] Chinese: add translation of stable_kernel_rules.txt |
| Andrew Morton | -mm merge plans for 2.6.23 |
| Arjan van de Ven | [Announce] Development release 0.1 of the LatencyTOP tool |
git: | |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | [GIT]: Networking |
| Stephen Hemminger | Re: iptables very slow after commit 784544739a25c30637397ace5489eeb6e15d7d49 |
