From: Dave Chinner <david@fromorbit.com>
To: Adam Sampson <ats@offog.org>
Cc: xfs@oss.sgi.com
Subject: Re: [ANNOUNCE] xfsprogs: v3.2.0 released!
Date: Sat, 17 May 2014 10:23:09 +1000 [thread overview]
Message-ID: <20140517002309.GA18954@dastard> (raw)
In-Reply-To: <y2a8uq11g5k.fsf@cartman.at.offog.org>
On Sat, May 17, 2014 at 12:02:15AM +0100, Adam Sampson wrote:
> Dave Chinner <david@fromorbit.com> writes:
>
> > It is my pleasure to announce the release of v3.2.0 of the xfsprogs
> > package.
>
> If this is built with DEBUG= (i.e. not defaulting to DEBUG=-NDEBUG),
> several source files fail to compile -- it looks like there are a number
> of assertions that haven't been updated for changes in the code:
Can't say I've ever built xfsprogs with "DEBUG=". I'm not sure
there's really any benefit in doing so - it's preferable to have
things like xfs_repair abort when it comes across an inconsistency
it can't handle than to continue blindly along and making a bigger
mess of the filesystem it's supposed to be fixing...
Anyway, we'll look to fix it for 3.2.1.
> (Errors from current Git, built with GCC 4.9. You also get a good crop
> of warnings if you build it with clang 3.4.1's scan-build, which'd be
> worth checking out in case there's anything serious there.)
ISTR that was done recently by Eric, and I've run clang recently,
too.
> > A signed gzipped-tar archive of the source code is available here:
>
> It's signed with a different key from the previous release -- it'd be
> useful to mention the key ID in the announcement so that it can be
> verified.
Should be obvious, yes? Especially with the release announcement
being signed, too. As it is, release tarballs have always been signed
with the current maintainer's key, so when the maintainer changes so
does the signing key....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-05-17 0:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 5:56 [ANNOUNCE] xfsprogs: v3.2.0 released! Dave Chinner
2014-05-16 23:02 ` Adam Sampson
2014-05-17 0:23 ` Dave Chinner [this message]
2014-05-17 1:01 ` Eric Sandeen
2014-05-17 10:53 ` Adam Sampson
2014-05-19 2:55 ` Dave Chinner
2014-05-20 8:27 ` 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=20140517002309.GA18954@dastard \
--to=david@fromorbit.com \
--cc=ats@offog.org \
--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