From: Wayne.Brown@altec.com
To: esr@thyrsus.com
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Keith Owens <kaos@ocs.com.au>,
CML2 <linux-kernel@vger.kernel.org>,
kbuild-devel@lists.sourceforge.net
Subject: Re: [kbuild-devel] Re: CML2 design philosophy heads-up
Date: Fri, 18 May 2001 15:04:43 -0500 [thread overview]
Message-ID: <86256A50.006E3D90.00@smtpnotes.altec.com> (raw)
On 05/18/2001 at 02:44:07 PM esr@thyrsus.com wrote:
>But the real question is whether the old tools have enough value to be
>worth the effort. What problem are you trying to solve here?
How about:
1. Some of us are perfectly satisfied with the existing tools and don't want
them to be yanked out from under us.
2. Some of us have no interest in Python and don't like being forced to deal
with installing/upgrading it just for CML2.
Wayne
next reply other threads:[~2001-05-18 20:06 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-18 20:04 Wayne.Brown [this message]
2001-05-18 20:43 ` [kbuild-devel] Re: CML2 design philosophy heads-up Alan Cox
2001-05-18 20:56 ` Mike Castle
-- strict thread matches above, loose matches on Subject: below --
2001-05-18 22:52 Wayne.Brown
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.006E3D90.00@smtpnotes.altec.com \
--to=wayne.brown@altec.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=esr@thyrsus.com \
--cc=kaos@ocs.com.au \
--cc=kbuild-devel@lists.sourceforge.net \
--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