From: Eric Sandeen <sandeen@sandeen.net>
To: David Chinner <dgc@sgi.com>
Cc: Niv Sardi <xaiki@cxhome.ath.cx>, Niv Sardi <xaiki@sgi.com>,
sgi.bugs.xfs@fido.engr.sgi.com, xfs-dev@sgi.com, xfs@oss.sgi.com
Subject: Re: ADD 977766 - mkfs.xfs man page needs the default settings updated. [REVIEW TAKE 3]
Date: Mon, 10 Mar 2008 20:45:57 -0500 [thread overview]
Message-ID: <47D5E455.9090309@sandeen.net> (raw)
In-Reply-To: <20080311011514.GE155407@sgi.com>
David Chinner wrote:
>> The change was motivated by Eric's comments on OSS that it is not
>> clear why one should pick log v1 or v2, and I believe he is right.
>
> If you don't understand - use the default. In most cases v2 logs are the
> right thing to use and no amount of text in the man page is going to be
> able to explain the corner cases where you'd want to use v1 logs....
I think the only problem, Dave, is that there are maybe 2 people on the
face of this earth who DO understand ;) (and I don't count myself among
them).
Just saying that v1 logs are still there for corner cases & specialized
workloads which may perform better is probably fine, don't you think?
That way those people who kill for such things can test both flavors.
Without that, people won't know if v1 is broken, deprecated, dangerous,
or what.
If you say nothing at all about the differences, then don't even bother
to document the log version option at all, IMHO.
-Eric
prev parent reply other threads:[~2008-03-11 1:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <incident_977766@bugworks.engr.sgi.com>
[not found] ` <20080222003514.8D88E2C3@toolshop.engr.sgi.com>
[not found] ` <nccskzlzg9f.fsf_-_@sgi.com>
[not found] ` <nccablbf8ra.fsf_-_@sgi.com>
[not found] ` <20080310060751.GY155407@sgi.com>
2008-03-10 6:15 ` ADD 977766 - mkfs.xfs man page needs the default settings updated. [REVIEW TAKE 3] Niv Sardi
2008-03-11 1:15 ` David Chinner
2008-03-11 1:45 ` Eric Sandeen [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=47D5E455.9090309@sandeen.net \
--to=sandeen@sandeen.net \
--cc=dgc@sgi.com \
--cc=sgi.bugs.xfs@fido.engr.sgi.com \
--cc=xaiki@cxhome.ath.cx \
--cc=xaiki@sgi.com \
--cc=xfs-dev@sgi.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