public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: XFS status update for November 2009
Date: Fri, 11 Dec 2009 08:22:13 -0500	[thread overview]
Message-ID: <20091211132213.GA22342@infradead.org> (raw)

November was a relatively slow month for XFS development.  The XFS tree
that is destined for the Linux 2.6.33 merge window saw a few fixes and
cleanups applied to it, and few important fixes still made it into the
last Linux 2.6.32 release candidates.  A few more patches including a
final version of the event tracing support for XFS were posted but not
reviewed yet.

On the userspace side there has been a fair amount of xfsprogs activity.
The repair speedup patches have finally been merged into the main development
branch and a couple of other fixes to the various utilities made it in, too.
The xfstests test suite saw another new regression test suite and a build
system fix up.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

                 reply	other threads:[~2009-12-11 13:21 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=20091211132213.GA22342@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