Re: Can't wait for '2.8 or 3.0',or maybe: 2.8 followed by 2.10 ??

[Martin J. Bligh]

>> > I think we should consider introduce a policy of having .*beaver.*
>> > names for each 2.6.x release, and maybe drop the version numbers
>> > altogether during 2.7.
>> > 
>> > John.
>> 
>> Sounds like a cool idea, but how are we supposed to know which "name"
>> is newer?
> 
> The names could be chosen alphabetically.  Rooster was mentioned for
> 2.7, but since 2.6 is beaver, I propose cock, as 'c' follows 'b'.

Oh great. 
So now we've progressed from flamewars to cock fighting on LKML. 

M.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/