linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: esr@thyrsus.com
To: jeff millar <jeff@wa1hco.mv.com>
Cc: linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net,
	"Eric S. Raymond" <esr@snark.thyrsus.com>
Subject: Re: CML2 1.0.0 doesn't remember configuration changes
Date: Wed, 11 Apr 2001 22:50:55 -0400	[thread overview]
Message-ID: <20010411225055.A11009@thyrsus.com> (raw)
In-Reply-To: <20010411191940.A9081@thyrsus.com> <E14nU6n-0007po-00@the-village.bc.nu> <20010411204523.C9081@thyrsus.com> <002701c0c2f1$fc672960$0201a8c0@home>
In-Reply-To: <002701c0c2f1$fc672960$0201a8c0@home>; from jeff@wa1hco.mv.com on Wed, Apr 11, 2001 at 09:43:08PM -0400

jeff millar <jeff@wa1hco.mv.com>:
> I'm confused.  Downloaded cml2-1.0.0 installed ran it....appear to work but
> it doesn't remember my changes.  Just now, I updated to 1.0.3 and it
> reported cleaning up existing files.  Ran "make config" and it popped up
> menu under X.  Then I changed the "config policy options" to "expert,
> wizard, tuning" and exited with "save and exit".
> 
> Then re-opened with make config and nothing changed...expert, wizard and
> tuning not set.  Maybe the program _knows_ I'm not a wizard but it should at
> least let me _tune_.  (joke)
> 
> By the way "make editconfig" shows the changes made under "make config" and
> allows me to make more changes..
> 
> The READ.ME says that "make config" will run configtrans to generate
> .config.  But that doesn't explain why "make config"  doesn't remember
> changes made to config.out.
> 
> ideas?
> 
> jeff

I think it's because I misunderstood how the standard productions are supposed
to work.  If you'll tell me what files you expect them to read on startup,
and in what order, I can emulate that behavior.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

The possession of arms by the people is the ultimate warrant
that government governs only with the consent of the governed.
        -- Jeff Snyder

  reply	other threads:[~2001-04-12  2:50 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 [this message]
2001-04-12  5:35                     ` jeff millar
2001-04-12  2:06                       ` esr
2001-04-12 21:20                         ` Ingo Oeser
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=20010411225055.A11009@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=esr@snark.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).