public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Arkadiusz Miskiewicz <arekm@maven.pl>
Cc: xfs@oss.sgi.com
Subject: Re: xfsprogs: update version numbers and changelog.
Date: Fri, 1 Feb 2013 16:54:50 -0600	[thread overview]
Message-ID: <20130201225450.GZ27055@sgi.com> (raw)
In-Reply-To: <20130201225103.GY27055@sgi.com>

Arkadiusz,

On Fri, Feb 01, 2013 at 04:51:03PM -0600, Ben Myers wrote:
> Update version numbers and changelog.
> 
> Signed-off-by: Ben Myers <bpm@sgi.com>
> 
> ---
> 
> Hi Folks,
> 
> This release is to address the problems in our last release reported by
> Arkadiusz Miśkiewicz.  It wouldn't build due to a missing source file and a
> build error when using -Werror=format-security.
>
> I have placed a pre-release tarball here:
> 
> ftp://oss.sgi.com/projects/xfs/cmd_tars/pre-release/xfsprogs-pre-3.1.11.tar.gz
> 
> It is fresh off the release.sh script with only the name changed to indicate
> that it is pre-release.  Please take a look and report any issues before next
> Wednesday.  If there are other patches which you feel are essential, now is the
> time to say so.

I neglected to cc you on this thread initially.  Could you take a look at the
tarball to see if it resolves the issue?

Regards,
	Ben

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

  reply	other threads:[~2013-02-01 22:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 22:51 xfsprogs: update version numbers and changelog Ben Myers
2013-02-01 22:54 ` Ben Myers [this message]
2013-02-02  6:01   ` Arkadiusz Miśkiewicz
  -- strict thread matches above, loose matches on Subject: below --
2013-03-19 21:08 Ben Myers

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=20130201225450.GZ27055@sgi.com \
    --to=bpm@sgi.com \
    --cc=arekm@maven.pl \
    --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