-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Forgive me if I missed it, but I've not seen any suggestions along the lines of this: how about just dropping the now-meaningless '.6' from the version string and retaining the rest. In other words: 2.27 2.27.1 ... 2.28 2.28.1 2.28.2 That way you continue the series in a meaningful way, whilst reverting to a neater 3-level numbering scheme again. Perhaps you could make 2.[6.]30 the switchover point.... Cheers AL - -- ==================================================================== ALASTAIR STEVENS * Web - www.altrux.me.uk * Blog - www.altrux.me.uk/blog.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIf8ITxW64B3bJb+wRAlxMAJ0cRiRBeN2MVBxauLudZDBQ9mEjEACfVx0C kNjXCycMZ+rxLvoMIVh0EAY= =04yz -----END PGP SIGNATURE----- --
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Chuck Ebbert | Why do so many machines need "noapic"? |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Natalie Protasevich | [BUG] New Kernel Bugs |
