mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Matt LaPlante" <laplam@rpi.edu>
To: <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] Unify CONFIG_LBD and CONFIG_LSF handling
Date: Wed, 21 Jun 2006 20:11:49 -0400	[thread overview]
Message-ID: <000501c69590$7535fee0$fe01a8c0@cyberdogt42> (raw)
In-Reply-To: <1150819141.2891.214.camel@laptopd505.fenrus.org>

> -----Original Message-----
> From: Arjan van de Ven [mailto:arjan@infradead.org]
> Sent: Tuesday, June 20, 2006 11:59 AM
> To: Roman Zippel
> Cc: Matthew Wilcox; Linus Torvalds; linux-kernel@vger.kernel.org;
> webmaster@cyberdogtech.com
> Subject: Re: [PATCH] Unify CONFIG_LBD and CONFIG_LSF handling
> 
> 
> > > 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.
> 
> N is not the safe answer; Y is. If you set it to N you can't read all
> your files (if there is a big one) etc etc.
> The safe-but-a-bit-slower answer really is Y.
> 

So should default be changed to Y?  It's currently N for kconfig, despite
the recommendation to the contrary.



      reply	other threads:[~2006-06-22  0:12 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
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 [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='000501c69590$7535fee0$fe01a8c0@cyberdogt42' \
    --to=laplam@rpi.edu \
    --cc=linux-kernel@vger.kernel.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®