From: Ben Myers <bpm@sgi.com>
To: xfs@oss.sgi.com
Cc: Nathan Scott <nathans@debian.org>
Subject: [patch 2/4] xfsprogs: update version and changelog
Date: Wed, 31 Oct 2012 14:25:23 -0500 [thread overview]
Message-ID: <20121031192545.866697061@sgi.com> (raw)
In-Reply-To: 20121031192521.163830089@sgi.com
[-- Attachment #1: xfsprogs-update-version --]
[-- Type: text/plain, Size: 2423 bytes --]
Update the version and changelogs for xfsprogs.
Signed-off-by: Ben Myers <bpm@sgi.com>
---
VERSION | 2 +-
configure.ac | 2 +-
debian/changelog | 6 ++++++
doc/CHANGES | 13 +++++++++++++
4 files changed, 21 insertions(+), 2 deletions(-)
Index: b/VERSION
===================================================================
--- a/VERSION 2012-10-31 13:28:44.911985637 -0500
+++ b/VERSION 2012-10-31 13:29:10.262026762 -0500
@@ -3,5 +3,5 @@
#
PKG_MAJOR=3
PKG_MINOR=1
-PKG_REVISION=8
+PKG_REVISION=9
PKG_BUILD=1
Index: b/configure.ac
===================================================================
--- a/configure.ac 2012-10-31 13:28:48.461946409 -0500
+++ b/configure.ac 2012-10-31 13:29:00.112026489 -0500
@@ -1,4 +1,4 @@
-AC_INIT([xfsprogs], [3.1.8])
+AC_INIT([xfsprogs], [3.1.9])
AC_PREREQ(2.50)
AC_CONFIG_AUX_DIR([.])
AC_CONFIG_MACRO_DIR([m4])
Index: b/debian/changelog
===================================================================
--- a/debian/changelog 2012-10-31 13:29:42.571323127 -0500
+++ b/debian/changelog 2012-10-31 13:30:43.452005833 -0500
@@ -1,3 +1,9 @@
+xfsprogs (3.1.9) unstable; urgency=low
+
+ * New upstream release
+
+ -- Nathan Scott <nathans@debian.org> Wed, 31 Oct 2012 13:29:00 +1100
+
xfsprogs (3.1.8) unstable; urgency=low
* New upstream release
Index: b/doc/CHANGES
===================================================================
--- a/doc/CHANGES 2012-10-31 13:29:34.521946743 -0500
+++ b/doc/CHANGES 2012-10-31 13:42:41.711835438 -0500
@@ -1,3 +1,16 @@
+xfsprogs-3.1.9 (31 October 2012)
+ - Print nice details if agsize is out of bounds in mkfs.xfs.
+ - Various fixes for fragmented multi-block dir2 handling in
+ xfs_repair.
+ - Fix extent record printing in xfs_db on big endian arches.
+ - Use the correct macros when dumping block maps in extent
+ form in xfs_db, thanks to Peter Watkins.
+ - Add sync file range support to xfs_io.
+ - Implement preadv/pwritev in xfs_io.
+ - Link against libreadline for libxcmd, thanks to Mike Frysinger.
+ - Clean up mkfs.xfs output on invalid inode size.
+ - Various build fixes, thanks to Mike Frysinger and Jan Engelhardt.
+
xfsprogs-3.1.8 (20 March 2012)
- Fix xfs_repair segfault on a corrupted filesystem by validating the
acl count before reading it.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev 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 ` Ben Myers [this message]
2012-10-31 19:25 ` [patch 3/4] xfsdump: " Ben Myers
2012-10-31 21:07 ` 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=20121031192545.866697061@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.