From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Eric S. Raymond" <esr@snark.thyrsus.com>
Cc: Peter Samuelson <peter@cadcamlab.org>,
linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net
Subject: Re: CML1 cleanup patch
Date: Mon, 26 Mar 2001 01:42:08 -0500 [thread overview]
Message-ID: <3ABEE4C0.36EB75F5@mandrakesoft.com> (raw)
In-Reply-To: <200103260001.f2Q01Yt09387@snark.thyrsus.com> <15038.56527.591553.87791@wire.cadcamlab.org> <3ABEE0B5.12A2F768@mandrakesoft.com>
Well, bummer. I can't seem to find Eric's message archived anywhere.
FWIW I am opposed to any large-scale cleanup of the configuration
language and/or identifiers in -any- 2.4.x series kernel.
Not only C code but installer utilities are affected by changes in the
CONFIG_xxx identifiers. If we change that namespace, we are changing
part of the API that is exported to drivers. Definitely not 2.4.x
stuff.
If we are moving to CML2 in 2.5, I see no point in big CML1 cleanups.
--
Jeff Garzik | May you have warm words on a cold evening,
Building 1024 | a full moon on a dark night,
MandrakeSoft | and a smooth road all the way to your door.
next prev parent reply other threads:[~2001-03-26 6:43 UTC|newest]
Thread overview: 24+ 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 [this message]
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 ` [kbuild-devel] " Keith Owens
2001-03-26 7:43 ` 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
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=3ABEE4C0.36EB75F5@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=esr@snark.thyrsus.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