public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <aelder@sgi.com>
To: xfs@oss.sgi.com
Subject: [PATCH] xfsdump: update summaries in preparation for release 3.0.6
Date: Wed, 05 Oct 2011 17:10:33 -0500	[thread overview]
Message-ID: <201110052210.p95MAXGI012463@stout.americas.sgi.com> (raw)

The following is a draft of summaries to be included in the next
release of xfsdump.

Signed-off-by: Alex Elder <alder@sgi.com>
---
 debian/changelog |    6 ++++++
 doc/CHANGES      |   26 ++++++++++++++++++++++++++
 2 files changed, 32 insertions(+)

Index: b/debian/changelog
===================================================================
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+xfsdump (3.0.6) unstable; urgency=low
+
+  * New upstream release
+
+ -- Nathan Scott <nathans@debian.org>  Wed,  5 Oct 2011 16:46:01 +1100
+
 xfsdump (3.0.5) unstable; urgency=low
 
   * New upstream release
Index: b/doc/CHANGES
===================================================================
--- a/doc/CHANGES
+++ b/doc/CHANGES
@@ -1,3 +1,29 @@
+xfsdump-3.0.6 (5 October 2011)
+	- Checksums available in various dump headers have now been
+	  enabled--unconditionally.  Previous Linux versions never
+	  appeared to have generated these.  A bug in generating the
+	  checksum for extended attributes was fixed, and the
+	  presence of this fix is now recorded with a different flag
+	  bit in the attribute header.
+	- Signal handling has been reworked to use a common signal
+	  handler and the POSIX signal API.  It has also been
+	  restructured a bit to be more amenable to a future
+	  conversion to using pthread model.
+	- A number of other changes have been implemented in
+	  preparation for support for multi-threaded dump and
+	  restore.
+	- Exit status for an individual restore stream is now
+	  properly reported to its parent process.
+	- Some areas of code have been refactored and cleaned up
+	  considerably.  Some dead code (always #ifdef'd) code has
+	  been eliminated.  Some other conditionally compiled
+	  code--always included--has been changed to be built
+	  unconditionally.
+	- Some dialogs, which were previously restricted to at most
+	  8 options, are now able to present up to 99.
+	- Ted Ts'o provided some improvements in support of building
+	  in a "hermetic" environment.
+
 xfsdump-3.0.5 (30 March 2011)
 	- Release tags will now be digitally signed
 	- Quota files will now be dumped, regardless of the maxsize

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

             reply	other threads:[~2011-10-05 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05 22:10 Alex Elder [this message]
2011-10-05 22:34 ` [PATCH] xfsdump: update summaries in preparation for release 3.0.6 Bill Kendall
2011-10-10 16:34 ` Christoph Hellwig
2011-10-13 10:43   ` Alex Elder

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=201110052210.p95MAXGI012463@stout.americas.sgi.com \
    --to=aelder@sgi.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