From: "Eric S. Raymond" <esr@thyrsus.com>
To: linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: State of CML2
Date: Wed, 4 Jul 2001 12:21:59 -0400 [thread overview]
Message-ID: <20010704122159.A11639@thyrsus.com> (raw)
I had kind of fallen out of the habit of posting release announcements here,
but now that 2.4.6 is out it seems a good time to review the situation.
The latest version is always available at <http://www.tuxedo.org/~esr/cml2/>.
The CML2 core is in good shape. There have been no serious bugs since
mid-April. The latest release (1.6.9) resynchronizes with 2.4.6 and ac24
and adds better compile-time type checking in expressions (thanks to
Daniel Junglas for getting me off the dime on this).
There are a couple of minor Tkinter weirdnesses remaining in the
xconfig interface, but they don't seem to show up in normal operation
with the Linux kernel rules file. They are fully described in the
distribution TODO file.
No speed complaints from the beta testers latelyl; the seige of tuning
in May seems to have worked. The requests I'm getting are pretty much
all for minor UI tweaks.
CML2 has another design win. The folks at Webmachines now use it to configure
the Linux distribution that they put in the flash ROMS of their network
apppliances. A lightly edited version of the Webmachines rulesfile is
available on the CML2 project site as an example.
The dungeon walls in CML2 adventure now occasionally feature entertaining
grafitti. Spot all the in-jokes and collect a valuable no-prize.
CML2 is ready.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
A true libertarian supports free enterprise, opposes big business;
supports local self-government, opposes the nation-state; supports the
National Rifle Association, opposes the Pentagon.
-- Edward Abbey
reply other threads:[~2001-07-04 16:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010704122159.A11639@thyrsus.com \
--to=esr@thyrsus.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