From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfsdump v3.1.4 released
Date: Fri, 18 Jul 2014 09:10:18 +1000 [thread overview]
Message-ID: <20140717231018.GH4453@dastard> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1231 bytes --]
Hello!
xfsdump v3.1.4 has just been released. This is a bug fix release
that contains fixes accumulated over the past year since the last
release.
The source code can be accessed via git using this URL:
git://oss.sgi.com/xfs/cmds/xfsdump.git
A signed gzipped-tar archive of the source code is available here:
ftp://oss.sgi.com/projects/xfs/cmd_tars/xfsdump-3.1.4.tar.gz
ftp://oss.sgi.com/projects/xfs/cmd_tars/xfsdump-3.1.4.tar.gz.sign
The archive is signed with my gpg key (the same one that this
release announcement is signed with).
Problems, issues, questions and general discussion about the release
should be directed to the XFS mailing list (xfs@oss.sgi.com).
A summary of the changes during development of this release (taken
from doc/CHANGES) is as follows:
- fix partial region segfault and debug code (Eric Sandeen)
- dump wholly sparse files correctly (Eric Sandeen)
- restore capabilities correctly
- memory leak fixes (Boris Ranto)
- sys_getdents modernisation (Kyle McMartin)
- Error message fixes (Iustin Pop)
- Updated polish translation (Jakub Bogusz)
- debian package build updates (Nathan Scott)
--
Dave Chinner
david@fromorbit.com
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2014-07-17 23:10 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=20140717231018.GH4453@dastard \
--to=david@fromorbit.com \
--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