From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs@oss.sgi.com
Subject: Re: [ANNOUNCE] xfsprogs: 3.2.0-rc2 release tagged
Date: Mon, 5 May 2014 09:15:48 +1000 [thread overview]
Message-ID: <20140504231548.GT26353@dastard> (raw)
In-Reply-To: <5364654C.3080009@sandeen.net>
[-- Attachment #1.1: Type: text/plain, Size: 1627 bytes --]
On Fri, May 02, 2014 at 10:41:00PM -0500, Eric Sandeen wrote:
> 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...
OK, I've uploaded a signed tarball to that location with the sha1sum
of:
93f3dd8818a749e718fd75e8dd48c466570a402c xfsprogs-3.2.0-rc2.tar.gz
FWIW, that set of "release" directories is a wasteland of old
releases, rpms, stuff moved out of the way because of mistakes, etc.
There is no consistent use of permissions or users, README files are
out of date, etc. Any suggestions on what should be done to clean
this up?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-05-04 23:16 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
2014-05-04 23:15 ` Dave Chinner [this message]
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=20140504231548.GT26353@dastard \
--to=david@fromorbit.com \
--cc=sandeen@sandeen.net \
--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).