From: Alex Elder <aelder@sgi.com>
To: XFS Mailing List <xfs@oss.sgi.com>
Subject: [ANNOUNCE] xfsprogs v3.1.2
Date: Fri, 07 May 2010 14:52:14 -0500 [thread overview]
Message-ID: <1273261934.2971.30.camel@doink> (raw)
Version 3.1.2 of xfsprogs has been released.
A gzipped-tar archive of the source code is available here:
ftp://oss.sgi.com/projects/xfs/cmd_tars/xfsprogs-3.1.2.tar.gz
The source code can be accessed via git using this URL:
git://oss.sgi.com/xfs/cmds/xfsprogs.git
Below is a summary (from the doc/CHANGES file) of changes
since release 3.1.1:
xfsprogs-3.1.2 (6 May 2010)
- Fix missing thread synchronization in xfs_repair duplicate
extent tracking.
- Fix handling of dynamic attribute fork roots in xfs_fsr.
- Fix sb_bad_features2 manipulations when tweaking the lazy
count flag.
- Add support for building on Debian GNU/kFreeBSD, thanks
to Petr Salinger.
- Improvements to the mkfs.xfs manpage, thanks to Wengang Wang.
- Various small blkid integration fixes in mkfs.xfs.
- Fix build against stricter system headers.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2010-05-07 19:50 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=1273261934.2971.30.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox