From: Roman Zippel <zippel@linux-m68k.org>
To: Jens Axboe <axboe@suse.de>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5 vi .config ; make oldconfig not working
Date: Wed, 6 Nov 2002 15:06:41 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.44.0211061457370.13258-100000@serv> (raw)
In-Reply-To: <20021105172110.GB1830@suse.de>
Hi,
On Tue, 5 Nov 2002, Jens Axboe wrote:
> > >axboe@burns:[.]linux-2.5-deadline-rbtree $ grep CONFIG_NFSD_V4 < .config
> > >641:CONFIG_NFSD_V4=y
> > >axboe@burns:[.]linux-2.5-deadline-rbtree $ vi .config
> > >axboe@burns:[.]linux-2.5-deadline-rbtree $ grep CONFIG_NFSD_V4 < .config
> > >641:CONFIG_NFSD_V4=n
> > >
> >
> > '=n' is wrong, that should be "# CONFIG_NFSD_V4 is not set" still...
>
> Why is that wrong? It worked before.
It was not documented and I only implemented that was documented. :)
It's of course no problem to change that.
bye, Roman
next prev parent reply other threads:[~2002-11-06 14:00 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
2002-11-06 14:06 ` Roman Zippel [this message]
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=Pine.LNX.4.44.0211061457370.13258-100000@serv \
--to=zippel@linux-m68k.org \
--cc=axboe@suse.de \
--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®