From: Keith Owens <kaos@ocs.com.au>
To: esr@thyrsus.com
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
"Eric S. Raymond" <esr@snark.thyrsus.com>,
Peter Samuelson <peter@cadcamlab.org>,
linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: [kbuild-devel] Re: CML1 cleanup patch
Date: Mon, 26 Mar 2001 17:28:44 +1000 [thread overview]
Message-ID: <23860.985591724@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Mon, 26 Mar 2001 02:09:02 EST." <20010326020902.C11181@thyrsus.com>
On Mon, 26 Mar 2001 02:09:02 -0500,
"Eric S. Raymond" <esr@thyrsus.com> wrote:
>Jeff Garzik <jgarzik@mandrakesoft.com>:
>> If we are moving to CML2 in 2.5, I see no point in big CML1 cleanups.
>
>Yes, I know, that's what I said about Peter's DERIVED patch a week ago.
Hey, that was my DERIVED patch, not Peter's. Point the blame where it
is due, even I think that my patch was a bad idea. -ENOTENOUGHCOFFEE.
The 20 cris variables must be renamed to CONFIG_xxx, otherwise make dep
will not find them and config changes will only cause partial
recompiles - or do the cris people like inconsistent kernels?
Correcting the two old names is obviously the right thing to do.
That just leaves the 17 names of the form CONFIG_[0-9]*. Only the 8139
is likely to affect outside the kernel and the argument that renaming
config options might affect external packages does not hold. The
recent aic7xxx change broke pcmcia on 2.2 kernels but we can work round
it.
next prev parent reply other threads:[~2001-03-26 7:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200103260001.f2Q01Yt09387@snark.thyrsus.com>
2001-03-26 6:08 ` CML1 cleanup patch Peter Samuelson
2001-03-26 6:24 ` Jeff Garzik
2001-03-26 6:42 ` Jeff Garzik
2001-03-26 7:09 ` Eric S. Raymond
2001-03-26 7:20 ` Jeff Garzik
2001-03-26 7:30 ` Eric S. Raymond
2001-03-26 7:37 ` Jeff Garzik
2001-03-26 7:28 ` Keith Owens [this message]
2001-03-26 7:43 ` [kbuild-devel] " Jeff Garzik
2001-03-26 7:52 ` Eric S. Raymond
2001-03-26 14:34 ` Rik van Riel
2001-03-26 6:49 ` Eric S. Raymond
2001-03-26 7:01 ` Jeff Garzik
2001-03-26 7:02 ` Alan Cox
2001-03-26 7:12 ` Eric S. Raymond
2001-03-26 14:43 ` Alan Cox
2001-03-26 7:22 ` Peter Samuelson
2001-03-26 7:40 ` Eric S. Raymond
2001-03-26 6:32 ` Eric S. Raymond
2001-03-26 11:57 ` [kbuild-devel] " John Cowan
2001-03-26 14:55 ` Rik van Riel
2001-03-26 17:54 ` Eric S. Raymond
2001-04-15 9:07 ` Kai Henningsen
2001-04-15 20:52 ` Olaf Titz
2001-03-26 7:33 Michael Elizabeth Chastain
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=23860.985591724@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=esr@snark.thyrsus.com \
--cc=esr@thyrsus.com \
--cc=jgarzik@mandrakesoft.com \
--cc=kbuild-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@cadcamlab.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