From: "John Stoffel" <john@stoffel.org>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [patch 00/20] 2.6.17-stable review
Date: Tue, 22 Aug 2006 09:49:29 -0400 [thread overview]
Message-ID: <17643.2921.654137.143271@stoffel.org> (raw)
In-Reply-To: <20060821214349.GA1885@suse.de>
>>>>> "Greg" == Greg KH <gregkh@suse.de> writes:
Greg> On Mon, Aug 21, 2006 at 03:46:16PM -0400, Dave Jones wrote:
>> On Mon, Aug 21, 2006 at 11:45:27AM -0700, Greg KH wrote:
>> > This is the start of the stable review cycle for the next 2.6.17.y
>> > release. There are 20 patches in this series, all will be posted as
>> > a response to this one. If anyone has any issues with these being
>> > applied, please let us know. If anyone is a maintainer of the proper
>> > subsystem, and wants to add a Signed-off-by: line to the patch, please
>> > respond with it.
>> >
>> > 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.
>>
>> Any chance of a 2.6.17.10-rc1 rollup patch again, like you did for .8?
Greg> Oops, forgot to do that, thanks for reminding me. It can be
Greg> found at:
Greg> http://www.kernel.org/pub/linux/kernel/people/gregkh/stable/patch-2.6.17.10-rc1.gz
Greg> And yes, it's not in the "main" v2.6 subdirectories, I'm not going to
Greg> put it there anymore as it confuses too many scripts/people.
So what if they're confused? If they're official releases, blessed
with holy penguin pee, then shouldn't they be in the standard release
area?
http://www.kernel.org/pub/linux/kernel/v2.6/
could just be extended down with a directory for each version
released, and the directory holds the ChangeLog, linux-... and
patch-... files.
Thanks for doing the stable branch in any case!
John
next prev parent reply other threads:[~2006-08-22 13:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060821183818.155091391@quad.kroah.org>
2006-08-21 18:45 ` [patch 00/20] 2.6.17-stable review Greg KH
2006-08-21 18:45 ` [patch 01/20] Have ext3 reject file handles with bad inode numbers early Greg KH
2006-08-21 18:45 ` [patch 02/20] sky2: phy power problem on 88e805x Greg KH
2006-08-21 18:46 ` [patch 03/20] Kill HASH_HIGHMEM from route cache hash sizing Greg KH
2006-08-21 18:46 ` [patch 04/20] Fix timer race in dst GC code Greg KH
2006-08-21 18:46 ` [patch 05/20] Fix IFLA_ADDRESS handling Greg KH
2006-08-21 18:46 ` [patch 06/20] Fix BeFS slab corruption Greg KH
2006-08-21 18:46 ` [patch 07/20] disable debugging version of write_lock() Greg KH
2006-08-21 18:46 ` [patch 08/20] ipx: header length validation needed Greg KH
2006-08-21 18:46 ` [patch 09/20] tpm: interrupt clear fix Greg KH
2006-08-21 18:46 ` [patch 10/20] : ulog: fix panic on SMP kernels Greg KH
2006-08-21 18:47 ` [patch 11/20] sys_getppid oopses on debug kernel Greg KH
2006-08-21 18:47 ` [patch 12/20] SERIAL: icom: select FW_LOADER Greg KH
2006-08-21 18:47 ` [patch 13/20] PCI: fix ICH6 quirks Greg KH
2006-08-21 18:47 ` [patch 14/20] : ip_tables: fix table locking in ipt_do_table Greg KH
2006-08-21 18:47 ` [patch 15/20] IA64: local DoS with corrupted ELFs Greg KH
2006-08-21 18:47 ` [patch 16/20] Fix ipv4 routing locking bug Greg KH
2006-08-21 18:47 ` Greg KH
2006-08-21 18:48 ` [patch 17/20] dm: BUG/OOPS fix Greg KH
2006-08-21 18:48 ` [patch 18/20] swsusp: Fix swap_type_of Greg KH
2006-08-21 18:48 ` [patch 19/20] MD: Fix a potential NULL dereference in md/raid1 Greg KH
2006-08-21 18:48 ` [patch 20/20] 1394: fix for recently added firewire patch that breaks things on ppc Greg KH
2006-08-22 9:03 ` Stefan Richter
2006-08-21 19:46 ` [patch 00/20] 2.6.17-stable review Dave Jones
2006-08-21 21:43 ` Greg KH
2006-08-22 13:49 ` John Stoffel [this message]
2006-08-22 13:59 ` Kyle Moffett
2006-08-22 14:53 ` John Stoffel
2006-08-22 19:13 ` Herbert Xu's paged unique skb trimming patch? Nix
2006-08-22 19:17 ` Greg KH
2006-08-22 20:41 ` David Miller
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=17643.2921.654137.143271@stoffel.org \
--to=john@stoffel.org \
--cc=gregkh@suse.de \
--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