public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Coywolf Qi Hunt <coywolf@gmail.com>
Cc: webmaster@kernel.org, lkml <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>,
	stable@kernel.org
Subject: Re: "stable" vs "security stable"
Date: Mon, 10 Oct 2005 12:14:03 -0400	[thread overview]
Message-ID: <434A934B.7050605@tmr.com> (raw)
In-Reply-To: <2cd57c900510090138h664e6c7eyad534f556b464c46@mail.gmail.com>

Coywolf Qi Hunt wrote:
> On 10/9/05, Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
> 
>>On Sun, 09 Oct 2005 15:44:38 +0800, Coywolf Qi Hunt said:
>>
>>>On 10/9/05, Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote:
>>
>>>It is "security stable". Let's take this new notation from now on.
>>>"Security Stable" doesn't have to be all security related.
>>
>>Tell you what - you convince the -stable team, and I'll go along with it..
>>
> 
> 
> Better be "stable" and "base". 2.6.13.3 is the latest stable, 2.6.13
> is the latest base.

I think the idea of having the most recent "base release," and -stable, 
and -rc, and -git, are desirable, with some clear terms. Those of us who 
started with ftp and never felt the need for using a GUI have long since 
learned what to keep and where to find it, but I bet most people use the 
web by now.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

  reply	other threads:[~2005-10-10 16:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-09  6:07 "stable" vs "security stable" 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 [this message]
2005-10-09  8:09 ` [Security] " Chris Wright
2005-10-09  8:20   ` Coywolf Qi Hunt

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=434A934B.7050605@tmr.com \
    --to=davidsen@tmr.com \
    --cc=coywolf@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=torvalds@osdl.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