From: Coywolf Qi Hunt <coywolf@gmail.com>
To: Chris Wright <chrisw@osdl.org>
Cc: webmaster@kernel.org, security@kernel.org,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Security] "stable" vs "security stable"
Date: Sun, 9 Oct 2005 16:20:57 +0800 [thread overview]
Message-ID: <2cd57c900510090120i27de6d0g110a3ee104f7e4a3@mail.gmail.com> (raw)
In-Reply-To: <20051009080937.GS5856@shell0.pdx.osdl.net>
On 10/9/05, Chris Wright <chrisw@osdl.org> wrote:
> * Coywolf Qi Hunt (coywolf@gmail.com) wrote:
> > I find the kernel.org first page inconvenient for some people somehow
> > since the security stable came.
>
> It's stable, not security stable. It does contain security fixes
> sometimes, but it is generally about patches that improve kernel
> stability.
OK, "stable" vs "base" now. 2.6.13.3 is the latest stable, and 2.6.13
is the latest base.
>
> > Now on the kernel.org page, we have 2.6.13.3 and 2.6.14-rc3. If one
> > wants to get 2.6.14-rc3, he shouldn't get 2.6.14-rc3 Full, but
> > 2.6.14-rc3 Patch and 2.6.13 Full, which isn't there unfortunately. I
> > suggest we name 2.6.13.3 "security stable", and 2.6.13 "stable".
>
> Perhaps a column B for base. Or just link to ketchup and be done with it.
>
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/
prev parent reply other threads:[~2005-10-09 8:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-09 6:07 Coywolf Qi Hunt
2005-10-09 7:14 ` Valdis.Kletnieks
2005-10-09 7:44 ` Coywolf Qi Hunt
2005-10-09 8:26 ` Valdis.Kletnieks
2005-10-09 8:38 ` Coywolf Qi Hunt
2005-10-10 16:14 ` Bill Davidsen
2005-10-09 8:09 ` [Security] " Chris Wright
2005-10-09 8:20 ` Coywolf Qi Hunt [this message]
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=2cd57c900510090120i27de6d0g110a3ee104f7e4a3@mail.gmail.com \
--to=coywolf@gmail.com \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=security@kernel.org \
--cc=webmaster@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
Powered by JetHome