From: Christoph Hellwig <hch@lst.de>
To: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: XFS status update for September 2008
Date: Wed, 1 Oct 2008 22:40:09 +0200 [thread overview]
Message-ID: <20081001204009.GA4259@lst.de> (raw)
With Linux 2.6.27 still not released but only making slow progress from
2.6.27-rc5 to 2.6.27-rc8 XFS changes in mainline have been minimal in
September with only about half a dozen bug fixes patches.
In the meantime the generic btree patch set has been committed to the
development tree, but not many other updates yet. On the user space side
xfsprogs 2.10.1 has been released on September 5th with a number of
important bug fixes. Following the release of xfsprogs 2.10.1 open season
for development of the user space code has started. The first full update
of the shared kernel / user space code in libxfs since 2005 has been
committed. In addition to that the number of headers installed for the
regular devel package has been reduced to the required minimum and support
for checking the source code for endianess errors using sparse has been
added.
The patch sets to unify the XFS and Linux inode structures, and rewrite
various bits of the sync code have seen various iterations on the XFS
list, but haven't been committed yet. A first set of patches implementing
CRCs for various metadata structures has been posted to the list.
reply other threads:[~2008-10-01 20:38 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=20081001204009.GA4259@lst.de \
--to=hch@lst.de \
--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