From: "Matt LaPlante" <laplam@rpi.edu>
To: "'Roman Zippel'" <zippel@linux-m68k.org>,
"'Matthew Wilcox'" <matthew@wil.cx>
Cc: "'Linus Torvalds'" <torvalds@osdl.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] Unify CONFIG_LBD and CONFIG_LSF handling
Date: Tue, 20 Jun 2006 11:53:24 -0400 [thread overview]
Message-ID: <000601c69481$a9f86c40$fe01a8c0@cyberdogt42> (raw)
In-Reply-To: <Pine.LNX.4.64.0606201742280.12900@scrub.home>
> On Tue, 20 Jun 2006, Matthew Wilcox wrote:
>
> > On Tue, Jun 20, 2006 at 04:20:53PM +0200, Roman Zippel wrote:
[snip]
> >
> > I don't really understand the complaint. If <rare condition applies>,
> > say Y, otherwise say N. If unsure, say Y. The default is N. Perhaps
> > all that's needed is to spell out the implications of saying Y? How
> > about:
> >
> > This option allows 32-bit systems to support files larger than
> > 2 Terabytes, at a cost of increased kernel memory usage. Most
> > people do not need the overhead and should answer N to this
> > question, but if you do not understand this question, answering
> > Y is safest.
> >
> > Or is that too verbose?
>
> How likely is it that someone who doesn't understand the question needs
> this option? I think N is a safe answer here.
>
> bye, Roman
This is the impression I had as well. Even if you disagree though, I was
equally confused by the fact that if we say to answer Y as default, why is
the kconfig default already N?
-
Matt LaPlante
next prev parent reply other threads:[~2006-06-20 15:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 22:16 Matthew Wilcox
2006-06-20 14:20 ` Roman Zippel
2006-06-20 14:52 ` Matthew Wilcox
2006-06-20 15:44 ` Roman Zippel
2006-06-20 15:53 ` Matt LaPlante [this message]
2006-06-20 16:01 ` Matthew Wilcox
2006-06-20 16:12 ` Roman Zippel
2006-06-20 16:48 ` Matthew Wilcox
2006-06-20 15:59 ` Arjan van de Ven
2006-06-22 0:11 ` Matt LaPlante
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='000601c69481$a9f86c40$fe01a8c0@cyberdogt42' \
--to=laplam@rpi.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=torvalds@osdl.org \
--cc=zippel@linux-m68k.org \
/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
all inboxes | Powered by JetHome®