All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: 2.5 vi .config ; make oldconfig not working
Date: Tue, 5 Nov 2002 17:50:24 +0100	[thread overview]
Message-ID: <20021105165024.GJ13587@suse.de> (raw)

Hi,

Can it really be that one cannot edit a config file and run make
oldconfig anymore? I'm used to editing an entry in .config and running
oldconfig to fix things up, now it just reenables the option. That's
clearly a major regression.

-- 
Jens Axboe


             reply	other threads:[~2002-11-05 16:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05 16:50 Jens Axboe [this message]
2002-11-05 17:08 ` 2.5 vi .config ; make oldconfig not working 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
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=20021105165024.GJ13587@suse.de \
    --to=axboe@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.