From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [ANNOUNCE] xfsprogs: master branch updated to v3.2.3-rc1
Date: Mon, 11 May 2015 17:23:35 +1000 [thread overview]
Message-ID: <20150511072335.GC15721@dastard> (raw)
In-Reply-To: <20150511053523.GA29703@infradead.org>
On Sun, May 10, 2015 at 10:35:23PM -0700, Christoph Hellwig wrote:
> 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.
I don't really think it is necessary. SLES 12 is already using CRCs
as the default XFS configuration for filesystems created by YaST, so
the cat is already out of the bag. And, historically speaking,
changing mkfs defaults has never been considered a compelling reason
to do a major/minor version bump so I haven't even bothered trying
to argue for that as I've never been successful in the past...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-05-11 7:23 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
2015-05-11 7:23 ` Dave Chinner [this message]
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=20150511072335.GC15721@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.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