From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: 3 years since last 2.2 release, why still on kernel.org main page?
Date: Sun, 13 May 2007 19:57:15 -0400 [thread overview]
Message-ID: <4647A5DB.2070205@tmr.com> (raw)
In-Reply-To: <200705102334.44077.rob@landley.net>
Rob Landley wrote:
> Out of curiosity, since 2.2 hasn't had a release in 3 years, and the last
> prepatch was 2 years ago, why is its' status still on the kernel.org main
> page?
>
> Not exactly something people are checking the status of on a daily basis...
>
> Just wondering...
>
I assume because it's a handy place to the the current 2.2 kernel, which
some people run for reasons which are valid to them.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2007-05-13 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 3:34 3 years since last 2.2 release, why still on kernel.org main page? Rob Landley
2007-05-13 23:57 ` Bill Davidsen [this message]
2007-05-14 17:41 ` Rob Landley
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=4647A5DB.2070205@tmr.com \
--to=davidsen@tmr.com \
--cc=hpa@zytor.com \
--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