Willy Tarreau wrote:I like the OpenBSD versioning as well. But they only have two releases a year, so their number should grow slower. Using the same versioning to linux will end up getting us to very large numbers that have no meaning. It's basically the same as what's going on now. I think using the year is the best idea. For instance, debian etch comes with linux 2.6.18, it would be nice if the users could easily know how old that actually is. I think 8.X for 2008, 9.X for 2009 should be great. It's good enough so none (or almost none) of us will live to see a need for changing it. Assuming people from 2101 would rather see 1.X than 101.X. Anyhow, will linux even survive that long with the same name, development model, etc? Not very likely. --
| James Bottomley | Breakage caused by unreviewed patch in x86 tree |
| Andrew Morton | Re: POHMELFS high performance network filesystem. Transactions, failover, performa... |
| Randy Dunlap | Re: 2.6.25-rc5-mm1 (paravirt/vsmp/no PCI) |
| Arnd Hannemann | 2.6.24-rc8 hangs at mfgpt-timer |
| Theodore Ts'o | Re: SVGA-alphanum. modes |
| Joseph R. Pannon | More install questions |
| Paul Richards | Header files |
| Les Andrzejewski | X386/WD90C31/SUMSUNG SYNC MASTER 4 |
git: | |
| David Miller | Re: [BUG] New Kernel Bugs |
| David Miller | Re: iptables very slow after commit784544739a25c30637397ace5489eeb6e15d7d49 |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
