From: "Maciej Soltysiak" <solt@dns.toxicfilms.tv>
To: <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 13:46:33 +0100 [thread overview]
Message-ID: <00a501c3c564$fd4a91f0$0e25fe0a@southpark.ae.poznan.pl> (raw)
In-Reply-To: <200312181114.hBIBEMB3000252@81-2-122-30.bradfords.org.uk>
> 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.
How about a naming policy of something going along this:
Stag (2.2)
Wolfling (2.4)
Beaver (2.6)
Rooster (2.7)
Ostrich (2.8)
Sharkey (2.9)
Cheetah (3.0)
And all having names of animals. Like in Croatia, their local currency
has only pictures of animals and plants on the bills and coins.
Pretty nice and neutral. Also codenames might make it
sound less technical for buzzword-orientated folks in the media
and other users.
Oh, and you would know which is better becase you would
here one or the other more often in terms of something new and fresh.
Regards,
Maciej
next prev parent reply other threads:[~2003-12-18 12:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2003-12-18 16:26 ` bill davidsen
2003-12-18 21:03 ` Rob Landley
2003-12-19 0:32 ` Dan Brow
2003-12-18 17:06 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
2003-12-18 18:45 ` Jamie Lokier
2003-12-18 19:02 ` John Dee
2003-12-18 19:21 ` 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
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='00a501c3c564$fd4a91f0$0e25fe0a@southpark.ae.poznan.pl' \
--to=solt@dns.toxicfilms.tv \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®