From: mru@kth.se (Måns Rullgård)
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 20:37:49 +0100 [thread overview]
Message-ID: <yw1xd6al3oj6.fsf@kth.se> (raw)
In-Reply-To: 200312181921.34648.andrew@walrond.org
Andrew Walrond <andrew@walrond.org> writes:
> On Thursday 18 Dec 2003 4:38 pm, Chris Meadors wrote:
>>
>> 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?
--
Måns Rullgård
mru@kth.se
next prev parent reply other threads:[~2003-12-18 19:37 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
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 [this message]
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=yw1xd6al3oj6.fsf@kth.se \
--to=mru@kth.se \
--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.