public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wayne.Brown@altec.com
To: Mike Castle <dalgoda@ix.netcom.com>
Cc: CML2 <linux-kernel@vger.kernel.org>
Subject: Re: [kbuild-devel] Re: CML2 design philosophy heads-up
Date: Fri, 18 May 2001 17:52:05 -0500	[thread overview]
Message-ID: <86256A50.007D8D19.00@smtpnotes.altec.com> (raw)



On 05/18/2001 at 03:56:50 PM Mike Castle <dalgoda@ix.netcom.com> wrote:

>On Fri, May 18, 2001 at 03:04:43PM -0500, Wayne.Brown@altec.com wrote:
>> 1.  Some of us are perfectly satisfied with the existing tools and don't want
>>       them to be yanked out from under us.
>
>Then stay with 2.4.x
>

Since doing kernel upgrades is my whole reason for using the tools, that's not a
very helpful suggestion.  It's a little like saying, "If you don't like the way
the air smells, just stop breathing."

>> 2.  Some of us have no interest in Python and don't like being forced to deal
>>       with installing/upgrading it just for CML2.
>
>
>Some don't like installing/upgrading the following just for a kernel:
>
>gcc
>binutils
>modutils
>mount
>Not to mention netfilter.

I don't especially like upgrading these things, either, and don't do it unless I
absolutely have to (that's why I'm still on egcs-2.91.66), but the kernel is
important enough to be worth the trouble.  If I have to use CML2 to move into
2.5.x, then I will.  However, upgrading a programming language I don't use, just
so I can replace a perfectly good tool with one I don't want, in order to do a
job that's always been easy to accomplish with the existing tools... well, that
seems a lot like a solution in search of a problem.

Fortunately, Alan's response about someone re-writing CML2 in C offers hope for
at least part of the issue.

Wayne



             reply	other threads:[~2001-05-18 22:53 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-18 22:52 Wayne.Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-18 20:04 [kbuild-devel] Re: CML2 design philosophy heads-up Wayne.Brown
2001-05-18 20:43 ` Alan Cox
2001-05-18 20:56 ` Mike Castle
2001-05-18 17:11 Wayne.Brown
2001-05-18 15:09 Keith Owens
2001-05-18 15:39 ` Alan Cox
2001-05-18 15:58   ` [kbuild-devel] " Eric S. Raymond
2001-05-18 16:01     ` Alan Cox
2001-05-18 16:34       ` Eric S. Raymond
2001-05-18 16:43         ` Christoph Hellwig
2001-05-18 16:45         ` Arjan van de Ven
2001-05-18 17:17           ` Eric S. Raymond
2001-05-18 17:22             ` Arjan van de Ven
2001-05-18 17:25               ` Eric S. Raymond
2001-05-19  5:54           ` Ben Ford
2001-05-18 17:33         ` Alan Cox
2001-05-18 18:25           ` Eric S. Raymond
2001-05-18 19:13             ` Alan Cox
2001-05-18 19:44               ` Eric S. Raymond
2001-05-18 20:38                 ` Alan Cox
2001-05-19  1:49         ` Aaron Lehmann
2001-05-18 14:53 Eric S. Raymond
2001-05-18 15:38 ` Alan Cox
2001-05-18 16:04   ` Eric S. Raymond
2001-05-18 16:09     ` [kbuild-devel] " Christoph Hellwig
2001-05-18 16:43       ` Michael Meissner
2001-05-18 17:13         ` Arjan van de Ven
2001-05-18 17:22         ` Eric S. Raymond
2001-05-18 17:42           ` Christoph Hellwig
2001-05-18 17:42             ` Alan Cox
2001-05-18 18:28             ` John Cowan
2001-05-18 16:02 ` Kai Germaschewski
2001-05-05 23:27 Eric S. Raymond
2001-05-13 14:22 ` Jes Sorensen
2001-05-13 15:25   ` Eric S. Raymond
2001-05-15 20:32     ` Jes Sorensen
2001-05-15 21:33       ` Eric S. Raymond
2001-05-18 15:19         ` Jes Sorensen
2001-05-18 15:51           ` [kbuild-devel] " John Cowan
2001-05-18 15:58             ` Christoph Hellwig
2001-05-18 16:00               ` John Cowan
2001-05-18 17:15                 ` Mike Castle
2001-05-18 17:28                   ` Christoph Hellwig
2001-05-21  0:29             ` Jes Sorensen
2001-05-21  1:58               ` Mike Castle
2001-05-21  6:33                 ` Ben Ford
2001-05-21  9:55                   ` Jes Sorensen
2001-05-21 16:59                   ` Mike Castle
2001-05-21 17:03                     ` Alan Cox
2001-05-21  7:21                 ` arjan
2001-05-21  2:10               ` Robert M. Love
2001-05-21  2:35                 ` Jakob Østergaard
2001-05-21  5:01                   ` Mike Galbraith
2001-05-21  9:58                   ` Jes Sorensen
2001-05-21 15:36                     ` Tom Rini
2001-05-21 16:24                       ` Eric S. Raymond
2001-05-21  6:11                 ` Mike A. Harris
2001-05-21 12:08                   ` Robert M. Love
2001-05-21 12:29                     ` Alan Cox
2001-05-21 16:39                       ` Brent D. Norris
2001-05-21 17:48                         ` Eric S. Raymond
2001-05-21 15:18                   ` Wichert Akkerman
2001-05-21 15:21                     ` Alan Cox
2001-05-21 15:52                     ` Alexander Viro
2001-05-21  3:47               ` Nicolas Pitre
2001-05-18 16:22           ` Steven Cole
     [not found]   ` <0105210958040I.10237@spc.esa.lanl.gov>
     [not found]     ` <20010521090130.F9965@opus.bloom.county>
2001-05-21 16:13       ` Steven Cole

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=86256A50.007D8D19.00@smtpnotes.altec.com \
    --to=wayne.brown@altec.com \
    --cc=dalgoda@ix.netcom.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