mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: CML2 <linux-kernel@vger.kernel.org>, kbuild-devel@lists.sourceforge.net
Subject: CML2 1.3.3 is available
Date: Sun, 29 Apr 2001 23:23:12 -0400	[thread overview]
Message-ID: <20010429232312.A3775@thyrsus.com> (raw)

The latest version is always available at http://www.tuxedo.org/~esr/cml2/

Release 1.3.3: Sun Apr 29 23:00:33 EDT 2001
	* Resync with 2.4.4.
	* Help texts merged into symbols file; the `helpfile' declaration
	  is gone.  (Text is merged in from Documentation/Configure.help
	  at CML2 installation time.)
	* Tweaked the appearance of inactive help buttons by popular demand.

My clever plan worked.  Less than three hours after I pronounced 1.3.1
"stable", somebody turned in the first crash bug in three weeks.  Fortunately
it was pretty trivial to fix, a loose end from one of my speedups.  Fixed in
yesterday's 1.3.2.

The big news in this version is that all the help texts have been merged into
the CML2 rules files.  A typical symbol declaration now looks like this:

GONK_5523		'Support for B5523 adaptive gonkulator'	text
Say Y here to compile in support for the Bollix 5523 adaptive gonkulator.
.

Help texts are merged into the CML2 symbols file at CML2 installation time.
The `helpfile' declaration is gone.  Among other things, this means you no
longer need to run CML2 inside a kernel source tree; you can test the scripts 
anywhere.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

See, when the GOVERNMENT spends money, it creates jobs; whereas when the money
is left in the hands of TAXPAYERS, God only knows what they do with it.  Bake
it into pies, probably.  Anything to avoid creating jobs.
	-- Dave Barry

             reply	other threads:[~2001-04-30  3:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-30  3:23 Eric S. Raymond [this message]
2001-04-30  3:41 ` jdnfk kjhds
2001-05-01  6:46   ` meept (was:Re: CML2 1.3.3 is available) jdnfk kjhds

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=20010429232312.A3775@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

all inboxes | Powered by JetHome®