From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Cc: stable@kernel.org
Subject: Next 2.6.17-stable review cycle will be starting in about 24 hours
Date: Thu, 3 Aug 2006 00:48:50 -0700 [thread overview]
Message-ID: <20060803074850.GA28301@kroah.com> (raw)
This is a heads up that the next 2.6.17-stable review cycle will be
starting in about 24 hours. I've caught up on all pending -stable
patches that I know about and placed them in our queue, which can be
browsed online at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=tree;f=queue-2.6.17
If anyone sees that this queue is missing something that they feel
should get into the next 2.6.17-stable release, please let us know at
stable@kernel.org within the next 24 hours or so.
thanks,
greg k-h
next reply other threads:[~2006-08-03 7:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 7:48 Greg KH [this message]
2006-08-03 16:47 ` Next 2.6.17-stable review cycle will be starting in about 24 hours Marcel Holtmann
2006-08-03 17:00 ` [stable] " Greg KH
2006-08-04 0:53 ` Neil Brown
2006-08-04 5:41 ` Greg KH
2006-08-04 10:25 ` Marcel Holtmann
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=20060803074850.GA28301@kroah.com \
--to=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox