From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [ANNOUNCE] xfsprogs: v3.2.0-rc3 released
Date: Fri, 9 May 2014 15:44:01 +1000 [thread overview]
Message-ID: <20140509054401.GK26353@dastard> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1580 bytes --]
Hi folks,
The xfsprogs repository at git://oss.sgi.com/xfs/cmds/xfsprogs has
just been updated.
The new head of the master branch is commit:
593dbdd xfsprogs: v3.2.0-rc3 release
This will hopefully be the last release candidate for 3.2.0. This
update fixes a coupel of build warnings, updates the Debian package
changelogs for the release, fixes an xfs_repair regression and a
xfs_repair scalability issue exposed by files with hundreds of
thousands of extents.
The repository has been tagged (v3.2.0-rc3) and a tarball has been
uploaded to ftp://oss.sgi.com/projects/xfs/cmd_tars/ so you can pull
down the source whicever way you want.
Please test!
-Dave.
Commits since v3.2.0-rc2:
Dave Chinner (3):
[bbd3275] repair: don't unlock prefetch tree to read discontig buffers
[bb9ca6c] repair: don't grind CPUs with large extent lists
[593dbdd] xfsprogs: v3.2.0-rc3 release
Nathan Scott (3):
[b47c8ca] Fix 32 bit build warning in libxfs, xfs_daddr_t printing
[ce5da12] Fix msgfmt warning when building the German translation
[75b480d] Update debian changelog in preparation for pending release
Code Diffstat:
VERSION | 2 +-
debian/changelog | 7 +++++++
doc/CHANGES | 7 +++++++
libxfs/rdwr.c | 5 +++--
po/de.po | 1 +
repair/bmap.c | 40 +++++++++++++++++++++++++++++++++-------
repair/prefetch.c | 51 +++++++++++++++++++++++++--------------------------
7 files changed, 77 insertions(+), 36 deletions(-)
--
Dave Chinner
david@fromorbit.com
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2014-05-09 5:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140509054401.GK26353@dastard \
--to=david@fromorbit.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