mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Coywolf Qi Hunt <coywolf@gmail.com>
To: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>
Cc: webmaster@kernel.org, lkml <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>,
	security@kernel.org, stable@kernel.org
Subject: Re: "stable" vs "security stable"
Date: Sun, 9 Oct 2005 16:38:07 +0800	[thread overview]
Message-ID: <2cd57c900510090138h664e6c7eyad534f556b464c46@mail.gmail.com> (raw)
In-Reply-To: <200510090826.j998QG4H012803@turing-police.cc.vt.edu>

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.

> > (you want stable@kernel.org to replace security@kernel.org too?)
>
> You're the one who called it "security stable" ;)

My fault. I didn't realise stable@kernel.org exist, and CCed the wrong
list security@kernel.org.

>
> > What you did is so stupid to me to to use -R every time. -R implies
> > something wrong, and need to revert.
>
> Umm... my diff had *lower case* -r (recursive), not -R (revert)...

I mean `patch -R'.
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/

  reply	other threads:[~2005-10-09  8:38 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 [this message]
2005-10-10 16:14         ` Bill Davidsen
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=2cd57c900510090138h664e6c7eyad534f556b464c46@mail.gmail.com \
    --to=coywolf@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=security@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

all inboxes | Powered by JetHome®