From: Rich Johnston <rjohnston@sgi.com>
To: xfs-oss <xfs@oss.sgi.com>
Cc: Nathan Scott <nathans@debian.org>
Subject: xfsdump-3.1.3 pre-release please test!
Date: Wed, 1 May 2013 15:12:19 -0500 [thread overview]
Message-ID: <51817723.9090603@sgi.com> (raw)
Hi Folks,
Here are the changes for this release:
xfsdump-3.1.3 (1 May 2013)
- Fix a segfault in xfsrestore when a path name is too long,
thanks to Nigel Tamplin.
- Fix a backward compatibility problem. Dumps created with
version 3.1.2 where extended attributes are in use failed
to restore with v3.1.0 due to file header checksum errors.
Thanks to Fugazzi for reporting.
- Refactored release scripts to conform to using git archive.
- Changed the build process so that 'make deb' uses the same
process of creating a source tree as the release script.
I have placed a pre-release tarball here:
ftp://oss.sgi.com/projects/xfs/cmd_tars/pre-release/xfsdump-pre-3.1.3-3.tar.gz
Please take a look and report any issues before next Wednesday (08 May
2013). If there are other patches which you feel are essential, now is
the time to say so.
Regards
--Rich
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2013-05-01 20:12 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=51817723.9090603@sgi.com \
--to=rjohnston@sgi.com \
--cc=nathans@debian.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