Another point that came into my mind:
How many scripts and programs out there parse the kernel version number,
know about the 2.6 prefix, and might need an update if it changes?
Not a big deal if a change would indicate a big change like with the old
development model - but IMHO not worth it if there's no compelling
reason why we have to change the numbering at all.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--
| 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(). |
