From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [ANNOUNCE] xfsprogs: master branch updated to v3.2.3-rc1
Date: Sun, 10 May 2015 22:35:23 -0700 [thread overview]
Message-ID: <20150511053523.GA29703@infradead.org> (raw)
In-Reply-To: <20150511005524.GE16689@dastard>
On Mon, May 11, 2015 at 10:55:25AM +1000, Dave Chinner wrote:
> Hi folks,
>
> The xfsprogs repository at git://oss.sgi.com/xfs/cmds/xfsprogs has
> just been updated. This update is the first candidate for a
> v3.2.3 release, so please test and report any problems you find.
>
> The new head of the master branch is commit:
>
> c8c0837 xfsprogs: update for 3.2.3-rc1 release
FYI, I don't think enabling v5 file system without at least a minor
version bump makes sense. While I'm not fan of release number inflation
this might even be a case for a major number bump to 4.x.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-05-11 5:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 0:55 [ANNOUNCE] xfsprogs: master branch updated to v3.2.3-rc1 Dave Chinner
2015-05-11 5:35 ` Christoph Hellwig [this message]
2015-05-11 7:23 ` 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=20150511053523.GA29703@infradead.org \
--to=hch@infradead.org \
--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