From: "Andrew Rodland" <arodland@noln.com>
To: esr@thyrsus.com
Cc: linux-kernel@vger.kernel.org, relson@osagesoftware.com
Subject: Re: CML2 funkiness
Date: Thu, 03 Jan 2002 01:40:15 -0500 [thread overview]
Message-ID: <web-54809847@admin.nni.com> (raw)
In-Reply-To: <20020102100311.A7819@thyrsus.com>
I found it!
The culprit: a bit of confusion over 'private'.
All of the not-saved symbols were just guards for 'do we
want to display question X'... so they were marked
private, so as not to clutter up the kernel (I assume).
However, this prevents them from getting written to
.config/config.out as well! Easy fix is to un-private
them, long-term is (as I see it) either to create a new
equivalent to private that somehow lets the symbol get
written to defconfig, but prevents it from becoming a
kernel define, or just to blow it off and don't worry
about it, and leave them normal symbols. However, it's
1:30AM and I might be missing something.
--Andrew
On Wed, 2 Jan 2002 10:03:11 -0500
"Eric S. Raymond" <esr@thyrsus.com> wrote:
> David Relson <relson@osagesoftware.com>:
> > From past testing of CML2 I know it uses file
> config.out as its
> > "memory". Looking in it, I didn't see any CONFIG
> symbols for these symbols.
> >
> > There's definitely something here for Eric to fix!
>
> I'm on it.
> --
> <a href="http://www.tuxedo.org/~esr/">Eric S.
> Raymond</a>
>
> Live free or die; death is not the worst of evils.
> -- General George Stark.
next prev parent reply other threads:[~2002-01-03 6:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200201010217.g012H2d00406@lists.us.dell.com>
2002-01-02 14:03 ` CML2 funkiness Andrew Rodland
2002-01-02 15:10 ` David Relson
2002-01-02 15:03 ` Eric S. Raymond
2002-01-03 6:40 ` Andrew Rodland [this message]
2002-01-03 7:31 ` Eric S. Raymond
2002-01-03 11:28 ` Andrew Rodland
2002-01-03 0:25 ` Andrew Rodland
2002-01-03 0:25 ` Andrew Rodland
2002-01-03 0:26 ` Andrew Rodland
2002-01-03 1:42 ` Miles Lane
2002-01-03 2:05 ` Andrew Rodland
2002-01-03 9:42 ` Eric S. Raymond
2002-01-03 0:34 ` Andrew Rodland
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=web-54809847@admin.nni.com \
--to=arodland@noln.com \
--cc=esr@thyrsus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=relson@osagesoftware.com \
/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