From: "Eric S. Raymond" <esr@thyrsus.com>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: CML2 0.9.1 is available
Date: Sun, 7 Jan 2001 18:18:32 -0500 [thread overview]
Message-ID: <20010107181832.A5612@thyrsus.com> (raw)
The latest version is always available at http://www.tuxedo.org/~esr/cml2/
Release 0.9.1: Sun Jan 7 18:05:36 EST 2001
* Synchronized with 2.4.0 final.
* Fixed bugs in handling of -W and -D flags.
* "source" pathnames are now evaluated relative relative to the
directory of the including file, so it's now possible to compile
in a directory other than that of the rules file.
Special thanks to Giacomo Catenazzi, whose persistence about
reporting front-end bugs finally pushed me in the right direction to
find some obscure problems I had never been able to reproduce before.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
To stay young requires the unceasing cultivation of the ability to
unlearn old falsehoods.
-- Lazarus Long
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-07 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-07 23:18 Eric S. Raymond [this message]
2001-01-08 8:17 ` CML2 0.9.1 is available Peter Loje Hansen
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=20010107181832.A5612@thyrsus.com \
--to=esr@thyrsus.com \
--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