From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: XFS status update for March 2009
Date: Thu, 16 Apr 2009 16:14:26 -0400 [thread overview]
Message-ID: <20090416201426.GA6035@infradead.org> (raw)
Linux 2.6.29 has been released which includes major XFS updates like the
new generic btree code, a fully functional 32bit compat ioctl implementation
and the new combined XFS and Linux inode. (See previous status reports
for more details). A patch series to improve correctness and performance
has been posted but not yet applied. Various minor fixes and cleanups
have been sent to Linus for 2.6.30 which looks like it will be a minor
release for XFS after the big churn in 2.6.29.
On userspace a lot of time has been spent on fixing and improving the
build system shared by the various XFS utilities as well as various smaller
improvements leading to the xfsprogs and xfsdump 3.0.1 releases which are
still outstanding.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2009-04-16 20:15 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=20090416201426.GA6035@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