public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: xfs@oss.sgi.com
Cc: Nathan Scott <nathans@debian.org>
Subject: [patch 3/4] xfsdump: update version and changelog
Date: Wed, 31 Oct 2012 14:25:24 -0500	[thread overview]
Message-ID: <20121031192546.066642460@sgi.com> (raw)
In-Reply-To: 20121031192521.163830089@sgi.com

[-- Attachment #1: xfsdump-update-version --]
[-- Type: text/plain, Size: 2136 bytes --]

Update the version and changelogs for xfsdump.

Signed-off-by: Ben Myers <bpm@sgi.com>

---
 VERSION          |    2 +-
 configure.ac     |    2 +-
 debian/changelog |    6 ++++++
 doc/CHANGES      |    8 ++++++++
 4 files changed, 16 insertions(+), 2 deletions(-)

Index: b/VERSION
===================================================================
--- a/VERSION	2012-10-31 13:43:32.341946579 -0500
+++ b/VERSION	2012-10-31 13:43:37.308175271 -0500
@@ -3,5 +3,5 @@
 #
 PKG_MAJOR=3
 PKG_MINOR=1
-PKG_REVISION=0
+PKG_REVISION=1
 PKG_BUILD=1
Index: b/configure.ac
===================================================================
--- a/configure.ac	2012-10-31 12:38:45.091946723 -0500
+++ b/configure.ac	2012-10-31 12:38:50.411340762 -0500
@@ -1,4 +1,4 @@
-AC_INIT([xfsdump], [3.1.0])
+AC_INIT([xfsdump], [3.1.1])
 AC_PREREQ(2.50)
 AC_CONFIG_AUX_DIR([.])
 AC_CONFIG_MACRO_DIR([m4])
Index: b/debian/changelog
===================================================================
--- a/debian/changelog	2012-10-31 12:39:28.991322370 -0500
+++ b/debian/changelog	2012-10-31 12:41:27.522005796 -0500
@@ -1,3 +1,9 @@
+xfsdump (3.1.1) unstable; urgency=low
+
+  * New upstream release
+
+ -- Nathan Scott <nathans@debian.org>  Wed, 31 Oct 2012 12:39:11 +1100
+
 xfsdump (3.1.0) unstable; urgency=low
 
   * New upstream release
Index: b/doc/CHANGES
===================================================================
--- a/doc/CHANGES	2012-10-31 12:39:34.301323054 -0500
+++ b/doc/CHANGES	2012-10-31 12:47:12.751986030 -0500
@@ -1,3 +1,11 @@
+xfsdump-3.1.1 (31 October 2012)
+	- Save and restore 32 bit project ids correctly.
+	- German translation, thanks to Chris Leick.
+	- A few fixups to the German translation, thanks to Stefan Ring.
+	- An initial Polish translation, thanks to Jakub Bogusz.
+	- Various build system cleanups, thanks to Mike Frysinger, and
+	  Jan Engelhardt.
+
 xfsdump-3.1.0 (22 March 2012)
 	- Fix metadata restore on split files.
 	- Add a -D option to skip a recursive scan of the filesystem

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

  parent reply	other threads:[~2012-10-31 19:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-31 19:25 [patch 0/4] xfs-userspace: update version and changelogs Ben Myers
2012-10-31 19:25 ` [patch 1/4] xfstests: update version and changelog Ben Myers
2012-10-31 21:00   ` Nathan Scott
2012-11-01 16:20     ` Ben Myers
2012-10-31 19:25 ` [patch 2/4] xfsprogs: " Ben Myers
2012-10-31 19:25 ` Ben Myers [this message]
2012-10-31 21:07   ` [patch 3/4] xfsdump: " Nathan Scott
2012-10-31 21:13     ` Ben Myers
2012-10-31 19:25 ` [patch 4/4] dmapi: " Ben Myers
2012-10-31 19:51 ` [patch 0/4] xfs-userspace: update version and changelogs Rich Johnston

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=20121031192546.066642460@sgi.com \
    --to=bpm@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