From: Jens Axboe <axboe@suse.de>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5 vi .config ; make oldconfig not working
Date: Tue, 5 Nov 2002 19:15:33 +0100 [thread overview]
Message-ID: <20021105181533.GC3515@suse.de> (raw)
In-Reply-To: <20021105181403.GG17573@nic1-pc.us.oracle.com>
On Tue, Nov 05 2002, Joel Becker wrote:
> On Tue, Nov 05, 2002 at 06:21:10PM +0100, Jens Axboe wrote:
> > > '=n' is wrong, that should be "# CONFIG_NFSD_V4 is not set" still...
> >
> > Why is that wrong? It worked before.
>
> I've run into kernels where '=n' didn't work. The old-skool
Never ever had a problem with it, and I've compiled pretty much every
single kernel in the last handful of kernel cycles.
> canonical answer was "# CONFIG_FOO is not set", and that worked reliably
> in <2.5
Less handy, though.
--
Jens Axboe
next prev parent reply other threads:[~2002-11-05 18:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 16:50 Jens Axboe
2002-11-05 17:08 ` Jeff Garzik
2002-11-05 17:13 ` Dave Jones
2002-11-05 17:16 ` Jens Axboe
2002-11-05 17:21 ` Jeff Garzik
2002-11-05 17:14 ` Jens Axboe
2002-11-05 17:19 ` Jeff Garzik
2002-11-05 17:21 ` Jens Axboe
2002-11-05 18:14 ` Joel Becker
2002-11-05 18:15 ` Jens Axboe [this message]
2002-11-06 14:06 ` Roman Zippel
2002-11-06 14:13 ` Jens Axboe
2002-11-05 17:23 ` Randy.Dunlap
2002-11-05 17:26 ` Arjan van de Ven
2002-11-05 17:26 ` Jens Axboe
2002-11-05 17:27 ` Jens Axboe
2002-11-05 18:20 ` Alan Cox
2002-11-05 18:14 ` Jens Axboe
2002-11-05 19:30 ` Sam Ravnborg
2002-11-05 19:42 ` Petr Baudis
2002-11-05 20:51 ` Sam Ravnborg
2002-11-05 20:16 ` Peter H. Ruegg
2002-11-05 18:55 ` [PATCH] Allow 'n' as a symbol value in the .config file Petr Baudis
2002-11-05 18:59 ` Jens Axboe
2002-11-06 19:39 ` 2.5 vi .config ; make oldconfig not working Rob Landley
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=20021105181533.GC3515@suse.de \
--to=axboe@suse.de \
--cc=Joel.Becker@oracle.com \
--cc=jgarzik@pobox.com \
--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®