>>Советую слегка ознакомиться в историей.
>>Ветки 2.6.x не существует в природе, она существует только пока не инкрементировали
>>x составляющую номера. Если вы сможете привести факты где показывается что
>>ветка 2.6.x.y продолжала свое развитие после выхода 2.6.(x+1) версии - я
>>с удовольствием послушаю
>
>интересно наблюдать за тем как у бздшника не укладывается в голове политика
>нумерации релизов отличная от бзд :)
>
>технические моменты разобраны. остальное - дело вкуса ;)
да?
http://en.wikipedia.org/wiki/Linux_kernel
раздел - Version numbering.
4я цифра появилоась после 2.6.8 и означает только bugix release. аналог -p релизов в фре.
процитирую
===
The version number of the Linux kernel currently consists of four numbers, following a recent change in the long-standing policy of a three-number versioning scheme. For illustration, let it be assumed that the version number is composed thus: A.B.C[.D] (e.g. 2.2.1, 2.4.13 or 2.6.12.3). * The C number indicates the minor revision of the kernel. In the old three-number versioning scheme, this was changed when security patches, bugfixes, new features or drivers were implemented in the kernel. With the new policy, however, it is only changed when new drivers or features are introduced; minor fixes are handled by the D number.
* A D number first occurred when a grave error, which required immediate fixing, was encountered in 2.6.8's NFS code. However, there were not enough other changes to legitimize the release of a new minor revision (which would have been 2.6.9). So, 2.6.8.1 was released, with the only change being the fix of that error. With 2.6.11, this was adopted as the new official versioning policy. Bug-fixes and security patches are now managed by the fourth number, whereas bigger changes are only implemented in minor revision changes (the C number).
===
>>> A D number first occurred when a grave error, which required immediate fixing <<<
:)
