public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Rich Johnston <rjohnston@sgi.com>
To: xfs-external <xfs@oss.sgi.com>
Subject: Re: [ANNOUNCE] xfsprogs v3.1.11  PLEASE LOOK AT THIS
Date: Wed, 8 May 2013 14:12:46 -0500	[thread overview]
Message-ID: <518AA3AE.4090407@sgi.com> (raw)
In-Reply-To: <518A9E7E.7070402@sgi.com>

On 05/08/2013 01:50 PM, Rich Johnston wrote:
> I was about to send out the following:  Please note the deprecated
> statement, is it correct??????
>
OOPS I meant to get internal verification about the deprecated message 
first. Please disregard the above lines.


>
> Version 3.1.11 of xfsprogs has been released.
>
> The source code can be accessed via git using this URL:
>
>      git://oss.sgi.com/xfs/cmds/xfsprogs.git
>
> A gzipped-tar archive of the source code is available here:
>
>      ftp://oss.sgi.com/projects/xfs/cmd_tars/xfsprogs-3.1.11.tar.gz
>
> The development tree previously hosted on kernel.org for this code has
> been deprecated:
>
>      git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
>
Yes it is deprecated.

> Below is a summary (from the doc/CHANGES file) of changes
> since release 3.1.10:
>
> xfsprogs-3.1.11 (8 May 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.
>          - kill XLOG_SET
>          - 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
>          - mkfs.xfs no longer attempts to discard when -N option is used.
>          - Update 'make deb' to use tarball
>          - Sync up with log reservation changes in the kernel.
>          - Fix possible unallocated memory access in fiemap.
>          - Guard against string overflow in path_to_fspath.
>          - Fix setup_cursor array allocation.
>          - Fix free of unintialized pointer in xfs_acl_valid error path.
>          - Guard against path string overflows.
>          - Check strdup results properly in initallfs().
>          - Fix attribute no_change_count logic.
>          - Remove extraneous close() in fsrallfs().
>          - xfs_repair now skips the freelist scan of a corrupt agf
>            when in no-modify mode.
>          - xfs_db now skips freelist scans of corrupt agfs.
>          - Remove unconditional ASSERT(0) in xfs_repair.
>          - Reduce bb_numrecs in bno/cnt btrees when log consumes all agf
> space.
>          - Add depraction message for xfs_check.
>          - xfs_quota allow user or group names beginning with digits
> reported by
>            James Carter.
>          - Fix manpages and usage() spelling, errors and omissions.
>          - Validate the extent count is at least within the positive
>            range of a signed 32 bit integer before using it.
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

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

  reply	other threads:[~2013-05-08 19:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-08 18:50 [ANNOUNCE] xfsprogs v3.1.11 PLEASE LOOK AT THIS Rich Johnston
2013-05-08 19:12 ` Rich Johnston [this message]
2013-05-08 20:40   ` Eric Sandeen

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=518AA3AE.4090407@sgi.com \
    --to=rjohnston@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