From: "Holger Hoffstaette" <holger@wizards.de>
To: linux-ext4@vger.kernel.org
Subject: No ext4 patches in 2.6.29.1?
Date: Wed, 01 Apr 2009 12:40:53 +0200 [thread overview]
Message-ID: <pan.2009.04.01.10.40.42.313375@wizards.de> (raw)
Hi,
This is not a complaint or bug report. :)
I've been following the recent ext4 activity (purely as an interested user
already running ext4 everywhere) and am somewhat concerned that Chris
Wright's recent announcement of 2.6.29.1 does not seem to contain any ext4
related fixes, like the "brown paper bag" lock typo or others. Is this
just an oversight? I've had no problems with ext4 so far (knock on wood)
but reading about some of the bugs here I'd rather have fixes sooner than
later..release consistency, peace of mind and all that. Is this not how
the stable release process is meant to work?
Thanks for all your hard work.
Holger
next reply other threads:[~2009-04-01 10:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 10:40 Holger Hoffstaette [this message]
2009-04-01 16:34 ` No ext4 patches in 2.6.29.1? Theodore Tso
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=pan.2009.04.01.10.40.42.313375@wizards.de \
--to=holger@wizards.de \
--cc=linux-ext4@vger.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;
as well as URLs for NNTP newsgroup(s).