From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kerrnel.org
Subject: XFS status update for October 2012
Date: Fri, 30 Nov 2012 19:13:28 -0500 [thread overview]
Message-ID: <20121201001327.GA8992@infradead.org> (raw)
October saw the merge of the XFS development tree for Linux 3.7 into
mainline as well as a few additional fixes for this new work.
Linux 3.7 will be a fairly boring release as far as XFS is concerned,
the biggest user visible changes are an intelligent implementation of
the lseek SEEK_HOLE/SEEK_DATA calls, and finally the switch to use
the inode64 allocator by default.
The XFS development tree for Linux 3.8 started getting commits in
October as well, most notably a large cleanup of the periodic sync
code.
On the user space side we saw release candidate for the next releases
of the XFS tools. For xfsprogs the 3.1.9-rc1 release brings various
fixes in xfs_repair, especially dealing with directories as well as
various improvements in xfs_db and mkfs.xfs, three new commands for
xfs_io and a few user visible fixes to xfs_quota. The xfsdump 3.1.1-rc1
release adds a German string translation and support for 32-bit project
IDs. xfstests saw its usual stream of fixes, but also a new ext4-specific
test case and a switch to use the util-linux version of fstrim instead
of a bundled one. All user space projects saw various improvements to
the build system.
reply other threads:[~2012-12-01 0:13 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=20121201001327.GA8992@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kerrnel.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;
as well as URLs for NNTP newsgroup(s).