From: Dave Chinner <david@fromorbit.com>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: xfs@oss.sgi.com
Subject: Re: V5 format and man mkfs.xfs
Date: Wed, 18 Jun 2014 08:46:58 +1000 [thread overview]
Message-ID: <20140617224658.GJ9508@dastard> (raw)
In-Reply-To: <20140617152917.GA17378@citd.de>
On Tue, Jun 17, 2014 at 05:29:17PM +0200, Matthias Schniedermeyer wrote:
> On 17.06.2014 22:37, Dave Chinner wrote:
> > On Tue, Jun 17, 2014 at 10:26:51AM +0200, Matthias Schniedermeyer wrote:
> > > Hi
> > >
> > > How seriously meant is "V5 isn't experimental anymore"?
> >
> > "Fully supported" isn't a clear enough statement?
>
> I guess that was a "selective memory"-bug on my side.
>
> > > I ask because the man-page only mentions the syntax to enable it by
> > > accident. A.k.a. the backport of ftype to V4.
> > > (man-page of xfsprogs 3.2.0 in Debian-SID)
> >
> > That's intentional. V5 superblocks are an implementation detail that
> > most users don't even need to know about. They care about the name
> > of the features they are enabling at mkfs time, not the details of
> > the on-disk implementation of those features.
>
> The question still stands.
>
> The crc-option is only mentioned "by accident".
> Without the ftype backport there would be no mention of the "feature
> crc".
Ok, so you're not reporting that we don't mention V5 filesystems as
"V5" filesystems. You're reporting that the "-m crc" option is not
documented. That's an oversight, and needs to be fixed.
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-06-17 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 8:26 V5 format and man mkfs.xfs Matthias Schniedermeyer
2014-06-17 12:37 ` Dave Chinner
2014-06-17 15:29 ` Matthias Schniedermeyer
2014-06-17 22:46 ` Dave Chinner [this message]
2014-06-18 3:39 ` Greg Freemyer
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=20140617224658.GJ9508@dastard \
--to=david@fromorbit.com \
--cc=ms@citd.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.