From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: XFS status update for September 2012
Date: Tue, 30 Oct 2012 17:46:46 -0400 [thread overview]
Message-ID: <20121030214646.GA12771@infradead.org> (raw)
September saw the release of Linux 3.6 which included a slightly smaller
than usual XFS update:
51 files changed, 2607 insertions(+), 2455 deletions(-)
The bulk of the changes in Linux 3.6 is made up by native support for
discontinuous buffers, with various minor bug fixes and cleanups making up
the rest. In the meantime the mailing list was busy with multiple revisions
of the sync/unmount code rewrite, and the patch series to make the inode64
mount option remountable and the default.
On the user space side xfsprogs saw new support for the preadv, pwritev and
sync_file_range system calls in xfs_io as well as minor fixes to libxcmd and
mkfs.xfs, xfsdump grew support for dumping and restoring 32-bit project ids
and and saw an update to the German translation. Xfstests saw a large number
of fixes, and a single new test case.
reply other threads:[~2012-10-30 21:46 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=20121030214646.GA12771@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).