From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: XFS status update for October 2008
Date: Thu, 6 Nov 2008 11:04:52 -0500 [thread overview]
Message-ID: <20081106160452.GA28042@infradead.org> (raw)
Linux 2.6.27 released with all the bits covered in last month's report. It
did however miss two important fixes for regressions that a few people hit.
2.6.27.3 or later are recommended for use with XFS.
In the meantime the generic btree implementation, the sync reorganization
and after a lot of merge pain the XFS and VFS inode unification hit the
development tree during the time allocated for the merge window. No XFS
updates other than the two regression fixes also in 2.6.27.3 have made it
into mainline as of 2.6.28-rc3.
The only new feature on the list in October is support for the fiemap
interface that has been added to the VFS during the 2.6.28 merge window.
However there was lot of patch traffic consisting of fixes and respun
versions of previously known patches. There still is a large backlog of
patches on the list that is not applied to the development tree yet.
reply other threads:[~2008-11-06 16:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20081106160452.GA28042@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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