cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] gfs2-utils 3.1.2 Released
Date: Wed, 06 Jul 2011 14:55:07 +0100	[thread overview]
Message-ID: <4E14693B.7090401@redhat.com> (raw)

Hi,

gfs2-utils 3.1.2 has been released. This version features various bug 
fixes, compression for gfs2_edit savemeta, and improved translation 
infrastructure. See below for a full list of changes.

The source tarball is available from:

    https://fedorahosted.org/released/gfs2-utils/gfs2-utils-3.1.2.tar.gz

To report bugs or issues, please use:

    https://bugzilla.redhat.com/

Regards,

Andy Price
Red Hat File Systems


Changes since 3.1.1:

Abhijith Das (2):
       gfs2_convert: exits with success without doing anything
       gfs2_convert exits with success without doing anything

Andrew Price (5):
       gfs2_edit: Add compression to savemeta and restoremeta
       gfs2_utils: More error handling improvements
       gfs2-utils: quieten some new build warnings
       gfs2_edit: Fix savemeta compression for older zlibs
       gfs2-utils: Fix up make-tarball.sh

Benjamin Marzinski (1):
       gfs2_grow: write one rindex entry and then the rest

Bob Peterson (2):
       gfs2_edit savemeta was not saving some directory info
       fsck.gfs2 only rebuilds one missing journal at a time

Carlos Maiolino (5):
       Add i18n support to gfs2-utils
       Track translatable files
       gfs2_convert: Add i18n support
       gfs2_convert: set translatable strings
       i18n support: Add gfs2_convert to translatable list

Steven Whitehouse (1):
       Remove last traces of unlinked file from gfs2-utils



                 reply	other threads:[~2011-07-06 13:55 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=4E14693B.7090401@redhat.com \
    --to=anprice@redhat.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;
as well as URLs for NNTP newsgroup(s).