public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: xfs-oss <xfs@oss.sgi.com>
Subject: time for an xfsdump release?
Date: Mon, 14 Jul 2014 11:06:05 -0500	[thread overview]
Message-ID: <53C3FFED.5080301@sandeen.net> (raw)

There aren't a lot of changes since v3.1.3, but with the rate of change of xfsdump (slow), I wonder if it's worth cutting a point release to get these bugfixes out there:

b1d6979 remove ancient sys_getdents code paths
9ed517b xfsdump: getdents.c: clean up ifdef-hell around sys_getdents
c3a4db1 xfsdump: Fix memory and fd leak in invutil/stobj.c
a88c490 restore: don't trash file capabilities
0ece1a1 xfsdump: handle large, wholly-sparse files
151858e xfsdump: fix DEBUGPARTIALS build
1162bdb xfsdump: avoid segfault in partial_reg() in error case

Thanks,
-Eric

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

             reply	other threads:[~2014-07-14 16:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 16:06 Eric Sandeen [this message]
2014-07-15 10:20 ` time for an xfsdump release? Christoph Hellwig
2014-07-16  3:40 ` Nathan Scott
2014-07-16  3:56   ` Nathan Scott

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=53C3FFED.5080301@sandeen.net \
    --to=sandeen@sandeen.net \
    --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