From: Alex Elder <aelder@sgi.com>
To: xfs@oss.sgi.com
Subject: xfsprogs: update CHANGES file for release
Date: Wed, 30 Mar 2011 12:53:20 -0500 [thread overview]
Message-ID: <1301507600.2953.13.camel@doink> (raw)
Update the CHANGES file, in preparation for releasing xfsprogs 3.1.5.
Signed-off-by: Alex Elder <aelder@sgi.com>
---
doc/CHANGES | 15 +++++++++++++++
1 file changed, 15 insertions(+)
Index: b/doc/CHANGES
===================================================================
--- a/doc/CHANGES
+++ b/doc/CHANGES
@@ -1,3 +1,18 @@
+xfsprogs-3.1.5 (30 March 2011)
+ - Polish translation update
+ - xfs_repair now warns if running in low memory mode
+ - Phase 2 of xfs_repair is now multithreaded
+ - xfs_quota no longer attempts to get quota information if
+ not enabled
+ - Inode flags are now properly validated by xfs_repair
+ - Metadump now obfuscates all file names reliably
+ - xfs_io now supports the "fiemap" command, a more generic
+ form of the "bmap" command
+ - xfs_io now supports the "fpunch" command, as well as a
+ "-p" flag to the "fallocate command. Both implement hole
+ punching.
+ - A number of other bug fixes
+
xfsprogs-3.1.4 (9 November 2010)
- Add projid32bit handling to userspace, resolving type
sizing issues when dealing with 32 bit project ids.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-03-30 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 17:53 Alex Elder [this message]
2011-03-30 18:46 ` xfsprogs: update CHANGES file for release Christoph Hellwig
2011-03-30 19:37 ` [PATCH v2] " Alex Elder
2011-03-30 21:40 ` Nathan Scott
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=1301507600.2953.13.camel@doink \
--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 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.