public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: xfs@oss.sgi.com
Subject: xfsprogs: update version numbers and changelog.
Date: Fri, 1 Feb 2013 16:51:03 -0600	[thread overview]
Message-ID: <20130201225103.GY27055@sgi.com> (raw)

Update version numbers and changelog.

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

---

Hi Folks,

This release is to address the problems in our last release reported by
Arkadiusz Miśkiewicz.  It wouldn't build due to a missing source file and a
build error when using -Werror=format-security.

I have placed a pre-release tarball here:

ftp://oss.sgi.com/projects/xfs/cmd_tars/pre-release/xfsprogs-pre-3.1.11.tar.gz

It is fresh off the release.sh script with only the name changed to indicate
that it is pre-release.  Please take a look and report any issues before next
Wednesday.  If there are other patches which you feel are essential, now is the
time to say so.

Thanks,
	Ben

 VERSION      |    2 +-
 configure.ac |    2 +-
 doc/CHANGES  |   16 ++++++++++++++++
 3 files changed, 18 insertions(+), 2 deletions(-)

Index: b/VERSION
===================================================================
--- a/VERSION	2013-02-01 15:58:21.901976637 -0600
+++ b/VERSION	2013-02-01 15:58:34.481985938 -0600
@@ -3,5 +3,5 @@
 #
 PKG_MAJOR=3
 PKG_MINOR=1
-PKG_REVISION=10
+PKG_REVISION=11
 PKG_BUILD=1
Index: b/configure.ac
===================================================================
--- a/configure.ac	2013-02-01 15:58:26.081322209 -0600
+++ b/configure.ac	2013-02-01 15:58:40.061985574 -0600
@@ -1,4 +1,4 @@
-AC_INIT([xfsprogs], [3.1.10])
+AC_INIT([xfsprogs], [3.1.11])
 AC_PREREQ(2.50)
 AC_CONFIG_AUX_DIR([.])
 AC_CONFIG_MACRO_DIR([m4])
Index: b/doc/CHANGES
===================================================================
--- a/doc/CHANGES	2013-02-01 15:58:52.461947261 -0600
+++ b/doc/CHANGES	2013-02-01 16:25:00.901985526 -0600
@@ -1,3 +1,19 @@
+xfsprogs-3.1.11 (1 February 2013)
+	- Support for relative paths in xfs_quota thanks to Satoru Takeuchi.
+	- mkfs.xfs will always go into multidisk mode when filesystem
+	  geometry is specified on the command line.
+	- Document all commands in xfs_io.
+	- Remove setfl command from xfs_io.
+	- xfs_metadump will obfuscate symlinks by path component.
+	- mkfs.xfs no longer accepts geometry settings smaller than the
+	  physical sector size.
+	- xfs_logprint now supports multiply-logged inode fields and
+	  handles continued inode transactions correctly.
+	- Update release scripts to use git archive to address a
+	  missing source file reported by Arkadiusz Miśkiewicz
+	- Fix a build error with -Werror=format-security, reported
+	  by Arkadiusz Miśkiewicz
+
 xfsprogs-3.1.10 (13 December 2012)
 	- Update release script to make a source tarball.
 

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

             reply	other threads:[~2013-02-01 22:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 22:51 Ben Myers [this message]
2013-02-01 22:54 ` xfsprogs: update version numbers and changelog Ben Myers
2013-02-02  6:01   ` Arkadiusz Miśkiewicz
  -- strict thread matches above, loose matches on Subject: below --
2013-03-19 21:08 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=20130201225103.GY27055@sgi.com \
    --to=bpm@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