From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Chris Meadors <clubneon@hereintown.net>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Can't wait for '2.8 or 3.0',or maybe: 2.8 followed by 2.10 ??
Date: Thu, 18 Dec 2003 09:33:53 -0800 [thread overview]
Message-ID: <72060000.1071768833@flay> (raw)
In-Reply-To: <1071765527.12681.5.camel@clubneon.priv.hereintown.net>
>> > 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.
next prev parent reply other threads:[~2003-12-18 17:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 17:06 Can't wait for '2.8 or 3.0',or maybe: 2.8 followed by 2.10 ?? Balram Adlakha
2003-12-18 11:44 ` Vojtech Pavlik
2003-12-18 11:49 ` Grahame White
2003-12-18 16:29 ` bill davidsen
2003-12-18 16:38 ` Chris Meadors
2003-12-18 17:33 ` Martin J. Bligh [this message]
2003-12-18 18:45 ` Jamie Lokier
2003-12-18 19:02 ` John Dee
2003-12-18 19:16 ` [SILLY] Can't wait for '2.8 or 3.0' Maciej Soltysiak
2003-12-18 19:21 ` Can't wait for '2.8 or 3.0',or maybe: 2.8 followed by 2.10 ?? Andrew Walrond
2003-12-18 19:37 ` Måns Rullgård
2003-12-18 20:22 ` Andrew Walrond
2003-12-19 1:34 ` Maciej Zenczykowski
-- strict thread matches above, loose matches on Subject: below --
2003-12-18 6:33 Can't wait for 2.8 or 3.0 Dan Brow
2003-12-18 6:30 ` Can't wait for '2.8 or 3.0',or maybe: 2.8 followed by 2.10 ?? Monchi Abbad
2003-12-18 7:34 ` Dan Brow
2003-12-18 10:58 ` Maciej Zenczykowski
2003-12-18 11:14 ` John Bradford
2003-12-18 12:46 ` Maciej Soltysiak
2003-12-18 16:26 ` bill davidsen
2003-12-18 21:03 ` Rob Landley
2003-12-19 0:32 ` Dan Brow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=72060000.1071768833@flay \
--to=mbligh@aracnet.com \
--cc=clubneon@hereintown.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.