From: "Eric S. Raymond" <esr@thyrsus.com>
To: Bjorn Wesen <bjorn@sparta.lu.se>
Cc: "Eric S. Raymond" <esr@snark.thyrsus.com>,
torvalds@transmeta.com, alan@lxorguk.ukuu.org.uk,
trini@kernel.crashing.org, linux-kernel@vger.kernel.org,
kbuild-devel@lists.sourceforge.net
Subject: Re: CML1 cleanup patch, take 2
Date: Mon, 26 Mar 2001 08:06:58 -0500 [thread overview]
Message-ID: <20010326080658.A16485@thyrsus.com> (raw)
In-Reply-To: <200103260955.f2Q9tfo14568@snark.thyrsus.com> <Pine.LNX.3.96.1010326133257.7071A-100000@medusa.sparta.lu.se>
In-Reply-To: <Pine.LNX.3.96.1010326133257.7071A-100000@medusa.sparta.lu.se>; from bjorn@sparta.lu.se on Mon, Mar 26, 2001 at 01:39:07PM +0200
Bjorn Wesen <bjorn@sparta.lu.se>:
> On Mon, 26 Mar 2001, Eric S. Raymond wrote:
> > (2) Fix up 20 cris-architecture configuration symbols lacking a CONFIG_
> > prefix, so they obey CML1/CML2 conventions and can be detected by
> > `make dep', also static-analysis tools and consistency checkers.
> > This is a BUG FIX in CML1.
>
> No need for you to fret on this; it's partly fixed in the version in
> Alan's tree and the rest will be cleaned up in our next update.
Good! That will simplify my life a lot. Assuming Linus takes that ac patch.
Greg Banks may have suggested a tolerable solution to the other problem.
I'm working on it now.
--
<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>
There's a truism that the road to Hell is often paved with good intentions.
The corollary is that evil is best known not by its motives but by its
*methods*.
next prev parent reply other threads:[~2001-03-26 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-26 9:55 CML1 cleanup patch, take 2 Eric S. Raymond
2001-03-26 11:39 ` Bjorn Wesen
2001-03-26 13:06 ` Eric S. Raymond [this message]
2001-03-26 14:50 ` Jeff Garzik
2001-03-26 15:11 ` Tom Rini
2001-03-26 19:52 ` Jeff Garzik
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=20010326080658.A16485@thyrsus.com \
--to=esr@thyrsus.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bjorn@sparta.lu.se \
--cc=esr@snark.thyrsus.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=trini@kernel.crashing.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.