Can't wait for '2.8 or 3.0',or maybe: 2.8 followed by 2.10 ??
Quoted 5 lines · John Bradford
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?
Signature · 4 lines
- ( ) ascii ribbon campaign - against html mail X / \
Quoted 10 lines · Balram Adlakha
Quoted 5 lines · John Bradford
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?
Based on a logical storyline? ;)
Signature · 2 lines
Vojtech Pavlik SuSE Labs, SuSE CR
Quoted 9 lines · Balram Adlakha
Quoted 5 lines · John Bradford
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?
Well let's see there could be :
2.beaver.rolling
2.beaver.sparking
2.beaver.toking
2.beaver.passing
2.beaver.stoned
2.beaver.tripping
Grahame
In article <[email protected]>, Grahame White <[email protected]> wrote:
| On Thursday 18 December 2003 17:06, Balram Adlakha wrote: | > John Bradford ([email protected]) wrote: | > > 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? | | Well let's see there could be : | | 2.beaver.rolling | 2.beaver.sparking | 2.beaver.toking | 2.beaver.passing | 2.beaver.stoned | 2.beaver.tripping
I take back what I just said about letting someone else name the subversions ;-)
Signature · 3 lines
bill davidsen <[email protected]> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979.
Quoted 10 lines · Balram Adlakha
Quoted 5 lines · John Bradford
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'.
Signature · 1 line
Chris
Quoted 11 lines
Quoted 8 lines
Quoted 5 lines
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.
Quoted 5 lines · Martin J. Bligh
Quoted 2 lines
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.
Are you two aware of which body parts are sometimes called "beaver" and "cock"?
-- Jamie
see, that's the beauty of it. :)
Quoted 17 lines · Jamie Lokier
Quoted 4 lines · Martin J. Bligh
Quoted 2 lines
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.
Are you two aware of which body parts are sometimes called "beaver" and "cock"?
-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[SILLY] Can't wait for '2.8 or 3.0'
In reply to Jamie LokierQuoted 2 lines
Are you two aware of which body parts are sometimes called "beaver" and "cock"?
Hehe, the funny thing is, that I noticed it just now :-) Maybe let's skip the cock.
Anyway, the names, if any, should be non-offensive, could be from nature (eg.
plants, flowers, animals, stars, geology, geography, physics) and could somehow reflect the nature of the kernel branch.
Beaver's cool for 2.6. The name is nice, the animal is sweet. The sexual conotation
is not really that bad, but it should not be emphasized.
And the quote about the beaver getting out of detox is funny too.
With time we would decide on the next codename. So I am not into competition right now.
I might make a web based system for us to decide. First on the set of codenames proposed in some time for, say, 2.7 and then we could vote on them.
Regards,
Maciej
Quoted 3 lines · Chris Meadors
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'.
Being more than happy with beaver, I don't think I'd getting involved with de- bugging cock. I'd probably wait until Tit is released. I've always been fond of tits.
Quoted 8 lines · Andrew Walrond
Quoted 3 lines · Chris Meadors
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'.
Being more than happy with beaver, I don't think I'd getting involved with de- bugging cock. I'd probably wait until Tit is released. I've always been fond of tits.
You mean a variety of the small winged creatures that spend the days singing in the trees, aka birds?
Signature · 2 lines
Måns Rullgård [email protected]
Quoted 3 lines · Måns Rullgård
You mean a variety of the small winged creatures that spend the days singing in the trees, aka birds?
Absolutely. Blue tits are my favourites. Very common during the cold winter months in the UK.
Quoted 2 lines
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'.
I don't think cock is politically correct and marketing safe. Even chicken is better :)