From: Marcel Holtmann <marcel@holtmann.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: Next 2.6.17-stable review cycle will be starting in about 24 hours
Date: Thu, 03 Aug 2006 18:47:32 +0200 [thread overview]
Message-ID: <1154623652.3905.76.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <20060803074850.GA28301@kroah.com>
Hi Greg,
> 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.
instead of ext3-avoid-triggering-ext3_error-on-bad-nfs-file-handle.patch
it makes more sense to include the revised patches from Neil:
http://comments.gmane.org/gmane.linux.kernel/430323
It seems that these are not merged upstream, but my understanding was
that they were the best way to fix this. For RHEL4 we are going with
these two patches.
Linus, any reason why they are not merged yet?
Regards
Marcel
next prev parent reply other threads:[~2006-08-03 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 7:48 Greg KH
2006-08-03 16:47 ` Marcel Holtmann [this message]
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=1154623652.3905.76.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=greg@kroah.com \
--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
Powered by JetHome