From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Cc: nathans@debian.org
Subject: [PATCH] xfsdump: bump version and update changelog
Date: Tue, 12 Jan 2010 11:59:36 -0500 [thread overview]
Message-ID: <20100112165936.GA5085@infradead.org> (raw)
Including a debian changelog update Nathan sent me earlier.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: xfsdump-dev/debian/changelog
===================================================================
--- xfsdump-dev.orig/debian/changelog 2010-01-06 18:42:23.013011836 +0100
+++ xfsdump-dev/debian/changelog 2010-01-12 17:55:30.278005578 +0100
@@ -1,3 +1,9 @@
+xfsdump (3.0.4) unstable; urgency=low
+
+ * New bugfix release
+
+ -- Nathan Scott <nathans@debian.org> Tue, 12 Jan 2009 17:46:03 +1100
+
xfsdump (3.0.2) unstable; urgency=low
* New bugfix release
Index: xfsdump-dev/VERSION
===================================================================
--- xfsdump-dev.orig/VERSION 2010-01-12 17:50:51.818254512 +0100
+++ xfsdump-dev/VERSION 2010-01-12 17:51:01.847006343 +0100
@@ -3,5 +3,5 @@
#
PKG_MAJOR=3
PKG_MINOR=0
-PKG_REVISION=2
+PKG_REVISION=4
PKG_BUILD=1
Index: xfsdump-dev/doc/CHANGES
===================================================================
--- xfsdump-dev.orig/doc/CHANGES 2010-01-12 17:51:04.440274239 +0100
+++ xfsdump-dev/doc/CHANGES 2010-01-12 17:54:59.819255971 +0100
@@ -1,3 +1,8 @@
+xfsdump-3.0.4
+ - Improve xfsinvutil man page and argument processing.
+ - Fix timestamp handling on 64-bit architectures in xfsinvutil.
+ - Various build system improvements.
+
xfsdump-3.0.2 (9 May 2009)
- Update the Debian packaging and resolve xfsprogs dependencies.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-01-12 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 16:59 Christoph Hellwig [this message]
2010-01-12 19:00 ` [PATCH] xfsdump: bump version and update changelog 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=20100112165936.GA5085@infradead.org \
--to=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