From: David Woodhouse <dwmw2@infradead.org>
To: "Giacomo A. Catenazzi" <cate@dplanet.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kbuild [which is not only ...2]
Date: Sat, 16 Feb 2002 09:18:17 +0000 [thread overview]
Message-ID: <22527.1013851097@redhat.com> (raw)
In-Reply-To: <3C6E1F90.40404@dplanet.ch>
In-Reply-To: <3C6E1F90.40404@dplanet.ch>
cate@dplanet.ch said:
> I have some comment/explications about the thread about kbuild.
The thread isn't about kbuild. It's about <omitted>. Please do not confuse
the two or even mention them in the same mail. It only serves to promote the
confusion.
kbuild is far more obviously the right thing to do. The main objection to it
last time I saw a discussion was that it has a performance problem in
certain cases -- which I believe Keith is working on.
It's not clear to me that you asking for it to be reconsidered before that's
complete is useful.
--
dwmw2
next prev parent reply other threads:[~2002-02-16 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-16 9:00 kbuild [which is not only CML2] Giacomo A. Catenazzi
2002-02-16 9:16 ` Jeff Garzik
2002-02-16 9:18 ` David Woodhouse [this message]
2002-02-16 10:06 ` kbuild [which is not only ...2] Giacomo A. Catenazzi
2002-02-16 14:55 ` kbuild [which is not only CML2] John Levon
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=22527.1013851097@redhat.com \
--to=dwmw2@infradead.org \
--cc=cate@dplanet.ch \
--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