From: Greg KH <greg@kroah.com>
To: Abhijit Karmarkar <awk@google.com>
Cc: stable@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [stable] question regarding the -stable patch queue ?
Date: Mon, 20 Apr 2009 20:27:28 -0700 [thread overview]
Message-ID: <20090421032728.GA14175@kroah.com> (raw)
In-Reply-To: <88cc3e770904201826odfde9baodcf8c221a0296909@mail.gmail.com>
On Mon, Apr 20, 2009 at 06:26:53PM -0700, Abhijit Karmarkar wrote:
> hi,
>
> i am trying to find if a particular upstream commit [1] will appear in
> the next -stable release of 2.6.28 kernel.
Yes it will.
> i see this commit being marked as "-stable candidate". does that mean
> it will automatically make it to the next stable release?
Yes.
> or should i submit a patch against the latest 2.6.28 stable series, to
> have this patch queued up for next stable release (2.6.28.10). can
> someone please advice?
If you know that the commit that went into Linus's tree will not apply
to the 2.6.28-stable tree, please send an updated version to the
stable@kernel.org address.
> what is the recommend way to do this search ("will upstream patch X be
> included in the next stable release")? so i don't bug this list in
> future with similar queries.
Just ask stable@kernel.org about it. We've been a bit behind on
flushing out the -stable queue (right now my todo-stable mbox contains
399 emails I need to wade through), due to vacations and conferences.
I'm slowly getting there, sorry for the delay.
thanks for your patience,
greg k-h
next prev parent reply other threads:[~2009-04-21 3:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 1:26 question regarding the -stable patch queue ? Abhijit Karmarkar
2009-04-21 3:27 ` Greg KH [this message]
2009-04-21 17:37 ` [stable] " Abhijit Karmarkar
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=20090421032728.GA14175@kroah.com \
--to=greg@kroah.com \
--cc=awk@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 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.