public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: "Eric S. Raymond" <esr@snark.thyrsus.com>,
	torvalds@transmeta.com, alan@lxorguk.ukuu.org.uk,
	linux-kernel@vger.kernel.org, kbuild-devel@lists.sourceforge.net,
	cort@fsmlabs.com
Subject: Re: CML1 cleanup patch, take 2
Date: Mon, 26 Mar 2001 14:52:07 -0500	[thread overview]
Message-ID: <3ABF9DE7.48458988@mandrakesoft.com> (raw)
In-Reply-To: <200103260955.f2Q9tfo14568@snark.thyrsus.com> <3ABF574D.65CBD22@mandrakesoft.com> <20010326081157.H16672@opus.bloom.county>

Tom Rini wrote:
> On Mon, Mar 26, 2001 at 09:50:53AM -0500, Jeff Garzik wrote:
> > PPC guys:  this is a gratuitous renaming change that is not required.
> > If you have been following the "CML1 cleanup patch" thread, you see that
> > Eric is blindly dictating policy when he says that CONFIG_[0-9] needs to
> > be cleaned up.

> The counter point to this is what does "CONFIG_6xx" or 8xx mean?  It's as bad
> as CONFIG_Mxxx imho :)

No argument.. :)  I definitely encourage namespace cleanup in 2.5 -- but
please don't change an identifier just because it begins with a numeric
prefix...  Change it because it needs to be changed.

Best regards,

	Jeff


-- 
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.

      reply	other threads:[~2001-03-26 19:53 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
2001-03-26 14:50 ` Jeff Garzik
2001-03-26 15:11   ` Tom Rini
2001-03-26 19:52     ` Jeff Garzik [this message]

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=3ABF9DE7.48458988@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cort@fsmlabs.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox