From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [ANNOUNCE] xfsprogs: 3.2.0-rc2 release tagged
Date: Fri, 02 May 2014 22:41:00 -0500 [thread overview]
Message-ID: <5364654C.3080009@sandeen.net> (raw)
In-Reply-To: <20140503025800.GI26353@dastard>
On 5/2/14, 9:58 PM, Dave Chinner wrote:
> On Fri, May 02, 2014 at 07:26:21PM -0500, Eric Sandeen wrote:
>> On 5/1/14, 7:05 PM, Dave Chinner wrote:
>>> 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:
>>>
>>> 67fcc94 xfsprogs: v3.2.0-rc2 release
>>>
>>> This commit has been tagged with v3.2.0-rc2. I'd like everyone who
>>> can test this to test it, as all the issues that needed to be solved
>>> before a release coul dbe made have now been addressed. If there are
>>> no new regressions or critical issues reported in the next week or
>>> so, I will make an official 3.2.0 release. So, please test. :)
>>
>> Any chance for a signed tarball?
>
> Do we need one? I can generate one, but I'm not 100% sure where we
> are putting them up online....
The others are at ftp://oss.sgi.com/projects/xfs/cmd_tars/
I dunno, I think distros usually expect to be able to grab a
tarball...
-Eric
> Cheers,
>
> Dave.
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-05-03 3:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 0:05 [ANNOUNCE] xfsprogs: 3.2.0-rc2 release tagged Dave Chinner
2014-05-03 0:26 ` Eric Sandeen
2014-05-03 2:58 ` Dave Chinner
2014-05-03 3:41 ` Eric Sandeen [this message]
2014-05-04 23:15 ` Dave Chinner
2014-05-03 6:18 ` Nathan Scott
2014-05-04 21:55 ` Dave Chinner
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=5364654C.3080009@sandeen.net \
--to=sandeen@sandeen.net \
--cc=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;
as well as URLs for NNTP newsgroup(s).