From: "Eric S. Raymond" <esr@thyrsus.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: [kbuild-devel] CML2 1.9.7 is available
Date: Thu, 13 Dec 2001 03:49:30 -0500 [thread overview]
Message-ID: <20011213034930.A8337@thyrsus.com> (raw)
In-Reply-To: <20011212023556.A8819@thyrsus.com> <16992.1008153373@ocs3.intra.ocs.com.au>
In-Reply-To: <16992.1008153373@ocs3.intra.ocs.com.au>; from kaos@ocs.com.au on Wed, Dec 12, 2001 at 09:36:13PM +1100
Keith Owens <kaos@ocs.com.au>:
> OUCH! The output from make menuconfig has significantly more options
> than make oldconfig when given exactly the same input. I thought one
> of the selling points for CML2 was different front ends but with
> identical back end processing. I don't like the way that the resulting
> config varies when fed to different front ends.
Not a big deal -- all the produced config.outs are logically equivalent.
Your differences all consist of symbols saved out as n in one version and not
saved at all in the other. It *would* be serious cause for alarm if that
were not the case.
The simplification in the saveability-predicate logic I just did for
1.9.8 made may help solve this problem.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
.. a government and its agents are under no general duty to
provide public services, such as police protection, to any
particular individual citizen...
-- Warren v. District of Columbia, 444 A.2d 1 (D.C. App.181)
next prev parent reply other threads:[~2001-12-13 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 7:35 CML2 1.9.7 is available Eric S. Raymond
2001-12-12 10:36 ` [kbuild-devel] " Keith Owens
2001-12-13 8:41 ` Eric S. Raymond
2001-12-13 8:49 ` Eric S. Raymond [this message]
2001-12-13 16:29 ` Bjorn Helgaas
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=20011213034930.A8337@thyrsus.com \
--to=esr@thyrsus.com \
--cc=kaos@ocs.com.au \
--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 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.