From: Greg KH <greg@kroah.com>
To: Neil Brown <neilb@suse.de>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] Next 2.6.17-stable review cycle will be starting in about 24 hours
Date: Thu, 3 Aug 2006 22:41:31 -0700 [thread overview]
Message-ID: <20060804054131.GA1045@kroah.com> (raw)
In-Reply-To: <17618.39572.764990.76181@cse.unsw.edu.au>
On Fri, Aug 04, 2006 at 10:53:40AM +1000, Neil Brown wrote:
> The ext2 patch, on the other hand, should probably go in to stable.
>
> I include it below so you don't have to scrape it off the web page...
Thanks, I've queued this up for the next -stable release.
greg k-h
next prev parent reply other threads:[~2006-08-04 5:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 7:48 Next 2.6.17-stable review cycle will be starting in about 24 hours Greg KH
2006-08-03 16:47 ` Marcel Holtmann
2006-08-03 17:00 ` [stable] " Greg KH
2006-08-04 0:53 ` Neil Brown
2006-08-04 5:41 ` Greg KH [this message]
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=20060804054131.GA1045@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=neilb@suse.de \
--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