From: bpm@sgi.com
To: xfs@oss.sgi.com
Cc: Christoph Hellwig <hch@infradead.org>,
Nathan Scott <nathans@debian.org>,
bpm@sgi.com
Subject: [patch 1/1] xfsdump: update summaries in preparation for release
Date: Tue, 20 Mar 2012 15:43:17 -0500 [thread overview]
Message-ID: <20120321172813.301990261@sgi.com> (raw)
In-Reply-To: 20120320204316.811460772@sgi.com
[-- Attachment #1: update-summaries-xfsdump-2 --]
[-- Type: text/plain, Size: 2127 bytes --]
Signed-off-by: Ben Myers <bpm@sgi.com>
---
VERSION | 4 ++--
debian/changelog | 6 ++++++
doc/CHANGES | 15 +++++++++++++++
3 files changed, 23 insertions(+), 2 deletions(-)
Index: b/VERSION
===================================================================
--- a/VERSION 2012-03-20 15:05:19.306958556 -0500
+++ b/VERSION 2012-03-20 15:39:21.606353510 -0500
@@ -2,6 +2,6 @@
# This file is used by configure to get version information
#
PKG_MAJOR=3
-PKG_MINOR=0
-PKG_REVISION=6
+PKG_MINOR=1
+PKG_REVISION=0
PKG_BUILD=1
Index: b/debian/changelog
===================================================================
--- a/debian/changelog 2012-03-20 15:05:19.227119979 -0500
+++ b/debian/changelog 2012-03-20 15:39:52.546957236 -0500
@@ -1,3 +1,9 @@
+xfsdump (3.1.0) unstable; urgency=low
+
+ * New upstream release
+
+ -- Nathan Scott <nathans@debian.org> Mon, 19 Mar 2012 15:07:12 +1100
+
xfsdump (3.0.6) unstable; urgency=low
* New upstream release
Index: b/doc/CHANGES
===================================================================
--- a/doc/CHANGES 2012-03-20 15:05:19.267069696 -0500
+++ b/doc/CHANGES 2012-03-20 15:38:58.486342973 -0500
@@ -1,3 +1,18 @@
+xfsdump-3.1.0 (20 March 2012)
+ - Fix metadata restore on split files.
+ - Add a -D option to skip a recursive scan of the filesystem
+ when dumping.
+ - Fix a 1 byte overflow with empty lists, thanks to Mike Frysinger.
+ - Enable multi-stream support on Linux using pthreads.
+ - Fix handling of Ctrl-D in prompts.
+ - Obsolete SGI_XFSDUMP_SKIP_FILE extended attribute for excluding
+ files from dump.
+ - Fix restoration of extended attributes on the root directory.
+ - Use the full 32-bit inode generation number instead of 12-bit
+ generation number. Bump the dump format version to 3.
+ - Do not create parent directories for orphaned files during
+ list-only (-t option) restore.
+
xfsdump-3.0.6 (14 October 2011)
- Unconditionally add checksums to various dump headers in
xfsdump.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-03-21 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 20:43 [patch 0/1] xfsdump: update summaries for 3.1.0 release bpm
2012-03-20 20:43 ` bpm [this message]
2012-03-21 18:02 ` [patch 1/1] xfsdump: update summaries in preparation for release Christoph Hellwig
2012-03-21 18:57 ` Nathan Scott
-- strict thread matches above, loose matches on Subject: below --
2012-03-19 20:42 [patch 0/1] xfsdump: update summaries for 3.0.7 release bpm
2012-03-19 20:42 ` [patch 1/1] xfsdump: update summaries in preparation for release bpm
2012-03-19 22:31 ` Christoph Hellwig
2012-03-20 18:18 ` Ben Myers
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=20120321172813.301990261@sgi.com \
--to=bpm@sgi.com \
--cc=hch@infradead.org \
--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