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. --
| Linus Torvalds | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Mike Galbraith | Re: regression: CD burning (k3b) went broke |
| Con Kolivas | Re: -mm merge plans for 2.6.23 |
git: | |
| Gerrit Renker | [PATCH 24/37] dccp: Processing Confirm options |
| Linus Torvalds | Re: [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Woodhouse | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
