From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: XFS status update for April 2010
Date: Sat, 8 May 2010 15:08:43 -0400 [thread overview]
Message-ID: <20100508190843.GA20445@infradead.org> (raw)
In April 2.6.34 still was in the release candidate phase, with
a hand full of XFS fixes making it into mainline. Development for
the 2.6.35 merge window went ahead full steam at the same time.
While a fair amount of patches hit the development tree these were
largely cleanups, with the real development activity happening on
the mailing list. There was another round of patches and following
discussion on the scalable busy extent tracking and delayed logging
features mentioned last month. They are expected to be merged in
May and queue up for the Linux 2.6.35 window. Last but not least
April saw a large number of XFS fixes backported to the 2.6.32 and
2.6.33 -stable series.
In user land xfsprogs has seen few but important updates, preparing
for a new release next month. The xfs_repair tool saw a fix to
correctly enable the lazy superblock counters on an existing
filesystem, and xfs_fsr saw updates to better deal with dynamic
attribute forks. Last but not a least a port to Debian GNU/kFreeBSD
got merged. The xfstests test suite saw two new test cases and various
smaller fixes.
reply other threads:[~2010-05-08 19:08 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=20100508190843.GA20445@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