public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Andi Kleen <ak@muc.de>
Cc: Greg KH <greg@kroah.com>, Chris Wright <chrisw@osdl.org>,
	torvalds@osdl.org, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] -stable, how it's going to work.
Date: Wed, 9 Mar 2005 11:20:30 -0300	[thread overview]
Message-ID: <20050309142029.GC15110@logos.cnet> (raw)
In-Reply-To: <m1sm35w3am.fsf@muc.de>


> >  - Security patches will be accepted into the -stable tree directly from
> >    the security kernel team, and not go through the normal review cycle.
> >    Contact the kernel security team for more details on this procedure.
> 
> This also sounds like a bad rule. How come the security team has more
> competence to review patches than the subsystem maintainers?  I can
> see the point of overruling maintainers on security issues when they
> are not responsive, but if they are I think the should be still the
> main point of contact.

The security team is going to work with the subsystem maintainers,
not overrule them.

That would be indeed insane.

  parent reply	other threads:[~2005-03-09 18:51 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09  7:28 [RFC] -stable, how it's going to work Greg KH
2005-03-09  9:56 ` Andi Kleen
2005-03-09 10:10   ` Arjan van de Ven
2005-03-09 10:17     ` Russell King
2005-03-09 10:24       ` Arjan van de Ven
2005-03-09 10:32         ` Russell King
2005-03-09 10:28       ` Andi Kleen
2005-03-09 14:20   ` Marcelo Tosatti [this message]
2005-03-09 18:00   ` Alan Cox
2005-03-09 18:29     ` Greg KH
2005-03-09 18:29     ` Chris Wright
2005-03-09 19:30     ` Andi Kleen
2005-03-09 18:28   ` Chris Wright
2005-03-09 19:44     ` Andi Kleen
2005-03-09 20:16       ` Chris Wright
2005-03-09 22:49       ` Russell King
2005-03-09 18:34   ` Greg KH
2005-03-09 19:39     ` Andi Kleen
2005-03-09 20:03       ` Greg KH
2005-03-09 20:25   ` Bill Davidsen
2005-03-10 10:00 ` Neil Brown
2005-03-10 10:17   ` Arjan van de Ven
2005-03-11  1:49     ` Neil Brown
2005-03-11  4:58       ` Chris Friesen
2005-03-11  7:07         ` Andi Kleen
2005-03-10 16:43   ` Greg KH
2005-03-10 17:27     ` Lee Revell
2005-03-10 17:31       ` Greg KH
2005-03-10 18:25         ` Lee Revell
2005-03-11 10:13           ` Pavel Machek
2005-03-10 17:43       ` Chris Wright
2005-03-10 17:51         ` Lee Revell
2005-03-10 17:44       ` Linus Torvalds
2005-03-11  0:10     ` Neil Brown
2005-03-11  2:43       ` J. Bruce Fields

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=20050309142029.GC15110@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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