Wow, only 5k. Since it is so trivial and often-asked-for,
this definately is one of the things to immediately
integrate in 2.3.0, just before it comes out.
> I see no bloat, only value added. Changes NOTHING for those
> who don't want it.
Maybe it's an idea to make a list of features that:
o are basically ready and stable
o were 'just' late for feature freeze
o are often requested
o are maintained
o are on the queue for 2.3
I am willing to put together that page. If you have
a patch/subsystem/other_thing that satisfies the
above requirements AND has it's own home page or
repository, please mail me the URL and a short
description.
I guess most newbie-hackers (ie. the ones with time
left) and sysadmins will be interested. Now if they
would have finished the beta-testing before 2.3
enters the market, we could be in for a short 2.3/2.4
cycle.
On a less realistic mode, what about only allowing 'ready'
stuff into 2.3 and starting with the code freeze in 2.3.5?
Rik -- typing slowly because my kbd is dvorak since sun 19:40...
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/