From: Christoph Hellwig <hch@lst.de>
To: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: XFS status update for September 2010
Date: Wed, 6 Oct 2010 05:41:52 -0400 [thread overview]
Message-ID: <20101006094152.GA24239@lst.de> (raw)
Mainline activity has been rather low in September while with only
two more fixes going into the 2.6.36 release candidates after the
large merge activity in August. Development for the next merge
window has been more active. The largest item was the inclusion
of the metadata scalability patch series, which provides very large
speedups for parallel metadata operations. In addition a new
ioctl to punch holes and convert the whole to an unwritten extent
was added and a small number of cleanups also made it into the tree.
Patches to add support for 32bit wide project ID identifiers and
using group and project quotas concurrently were posted to the list
and discussed but not yet included.
Userspace development has been rather quited again, with a single fix
committed to xfsprogs and xfsdump each. The xfstests test suite grew
a new test case and received a few additional fixes. Last but not least
the XFS Users Guide [1] was updated with various factual corrections
and spelling fixes.
[1] http://xfs.org/docs/xfsdocs-xml-dev/XFS_User_Guide//tmp/en-US/html/index.html
reply other threads:[~2010-10-06 9:41 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=20101006094152.GA24239@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