All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
	linux-kernel@vger.kernel.org,
	Stefan Bader <stefan.bader@canonical.com>,
	Tim Gardner <tim.gardner@canonical.com>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: Volunteering for stable patch review process
Date: Mon, 15 Jun 2009 22:50:54 -0700	[thread overview]
Message-ID: <20090616055054.GA31387@kroah.com> (raw)
In-Reply-To: <20090616053718.GE30071@sequoia.sous-sol.org>

On Mon, Jun 15, 2009 at 10:37:18PM -0700, Chris Wright wrote:
> * Luis R. Rodriguez (mcgrof@gmail.com) wrote:
> > I'm curious what the process is to join the group of volunteers to
> > review stable patches. Can't seem to find the docs for it. The only
> > excerpt I see is:
> > 
> > Review committee:
> > 
> >  - This is made up of a number of kernel developers who have volunteered for
> >    this task, and a few that haven't.
> 
> Just send a note (you just did) and we'll put you on the review list
> (I just did).

Also, the relevant text for how to join is in the 000/XXX message we
send out with every review, that contains the lines:

	These patches are sent out with a number of different people on the
	Cc: line.  If you wish to be a reviewer, please email stable@kernel.org
	to add your name to the list.  If you want to be off the reviewer list,
	also email us.

thanks,

greg k-h

  reply	other threads:[~2009-06-16  6:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16  5:30 Volunteering for stable patch review process Luis R. Rodriguez
2009-06-16  5:37 ` Chris Wright
2009-06-16  5:50   ` Greg KH [this message]
2009-06-16 18:32   ` Luis R. Rodriguez
2009-06-16 18:43     ` Stefan Bader
2009-06-16 18:49       ` Greg KH
2009-06-16 19:00         ` Chris Wright
2009-06-16 19:15           ` Greg KH
2009-06-16 20:00             ` Chris Wright

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=20090616055054.GA31387@kroah.com \
    --to=greg@kroah.com \
    --cc=chrisw@sous-sol.org \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=stefan.bader@canonical.com \
    --cc=tim.gardner@canonical.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.