linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: esr@thyrsus.com, jeff millar <jeff@wa1hco.mv.com>,
	linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: CML2 1.0.0 doesn't remember configuration changes
Date: Thu, 12 Apr 2001 23:20:21 +0200	[thread overview]
Message-ID: <20010412232021.A682@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20010411191940.A9081@thyrsus.com> <E14nU6n-0007po-00@the-village.bc.nu> <20010411204523.C9081@thyrsus.com> <002701c0c2f1$fc672960$0201a8c0@home> <20010411225055.A11009@thyrsus.com> <003c01c0c312$73713300$0201a8c0@home> <20010411220646.A12550@thyrsus.com>
In-Reply-To: <20010411220646.A12550@thyrsus.com>; from esr@thyrsus.com on Wed, Apr 11, 2001 at 10:06:46PM -0400

On Wed, Apr 11, 2001 at 10:06:46PM -0400, esr@thyrsus.com wrote:
> Editconfig was a mistake.  OK, I think I understand the rules now.  Is it:
> 
> (1) First, try to read from .config
> (2) If .config doesn't exist, read from $(ARCH)/defconfig
> 
> ?

Right. But with the following constraints:

   make oldconfig takes _any_ .config from _any_ kernel and builds a
   new one for _this_ kernel asking any remaining questions
   
   make xconfig, make menuconfig, make config take a .config from
   _this_ kernel and configure for _this_ kernel

   if they don't find and .config, then they fall back to
   $(ARCH)/defconfig


Would be nice, if CML2 works like this too, because it's not nice
to go through all the options again, if I install a new kernel or
just want to change my current kernel config add a module.

But your CML2 is sure great work.

Regards

Ingo Oeser
-- 
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
         <<<<<<<<<<<<     been there and had much fun   >>>>>>>>>>>>

  reply	other threads:[~2001-04-12 21:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-10 10:47 CML2 1.0.0 release announcement Eric S. Raymond
2001-04-10 12:14 ` Russell King
2001-04-11 19:43 ` davej
2001-04-11 20:04   ` Christoph Hellwig
2001-04-11 20:16     ` Dave Jones
2001-04-11 20:27       ` Christoph Hellwig
2001-04-11 22:23         ` Alan Cox
2001-04-11 23:19           ` esr
2001-04-11 23:30             ` Alan Cox
2001-04-11 23:33             ` Alan Cox
2001-04-12  0:45               ` esr
     [not found]                 ` <3AD4FC54.C86AACBE@mandrakesoft.com>
2001-04-12  1:28                   ` esr
2001-04-12  1:43                 ` CML2 1.0.0 doesn't remember configuration changes jeff millar
2001-04-12  2:50                   ` esr
2001-04-12  5:35                     ` jeff millar
2001-04-12  2:06                       ` esr
2001-04-12 21:20                         ` Ingo Oeser [this message]
2001-04-14  2:11                           ` Eric S. Raymond
2001-04-14  2:29                             ` Jeff Garzik
2001-04-14  4:33                               ` Nicolas Pitre
2001-04-12 10:45                 ` CML2 1.0.0 release announcement Alan Cox
2001-04-11 22:20   ` esr
2001-04-12  7:09 ` Albert D. Cahalan
2001-04-12  8:57   ` Jamie Lokier
2001-04-12 10:57   ` esr

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=20010412232021.A682@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=esr@thyrsus.com \
    --cc=jeff@wa1hco.mv.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --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;
as well as URLs for NNTP newsgroup(s).