public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Chris Wright <chrisw@osdl.org>
Cc: chrisw@osdl.org, akpm@osdl.org, Simon.Derr@bull.net,
	linux-kernel@vger.kernel.org, torvalds@osdl.org,
	stable@kernel.org
Subject: Re: [PATCH 2.6.13-stable] cpuset semaphore double trip fix
Date: Fri, 9 Sep 2005 20:40:54 -0700	[thread overview]
Message-ID: <20050909204054.1ba43ebd.pj@sgi.com> (raw)
In-Reply-To: <20050910032844.GH7762@shell0.pdx.osdl.net>

Chris wrote:
> OK, we can hold until you find a good case for triggering ;-)

Agreed.

By the way, you or Randy mentioned something about leaving a mention of
-stable in the MAINTAINERS file.

That wouldn't have helped me this week, but if you had put the string:

	Documentation/stable_kernel_rules.txt

somewhere in the opening text of the messages that announce stable
reviews, that would have saved me some time.  I have in mind the
lkml messages such as:

	From: Chris Wright <chrisw@osdl.org>
	To: linux-kernel@vger.kernel.org, stable@kernel.org
	Subject: [PATCH 0/9] -stable review
	
	This is the start of the stable review cycle for the 2.6.13.1 release.

Just a thought ...

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

      reply	other threads:[~2005-09-10  3:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-10  0:44 [PATCH 2.6.13-stable] cpuset semaphore double trip fix Paul Jackson
2005-09-10  1:56 ` Randy.Dunlap
2005-09-10  2:31   ` Paul Jackson
2005-09-10  3:01 ` Chris Wright
2005-09-10  3:20   ` Paul Jackson
2005-09-10  3:28     ` Chris Wright
2005-09-10  3:40       ` Paul Jackson [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=20050909204054.1ba43ebd.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=Simon.Derr@bull.net \
    --cc=akpm@osdl.org \
    --cc=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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