From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Giacomo A. Catenazzi" <cate@dplanet.ch>
Cc: linux-kernel@vger.kernel.org, kaos@ocs.com.au
Subject: Re: kbuild [which is not only CML2]
Date: Sat, 16 Feb 2002 04:16:05 -0500 [thread overview]
Message-ID: <3C6E2355.AA514ECA@mandrakesoft.com> (raw)
In-Reply-To: <3C6E1F90.40404@dplanet.ch>
"Giacomo A. Catenazzi" wrote:
> The discussion was also on lkml, ESR asked to kbuild
> people to give some comments, using also the feed-back
> of lkml.
> As you noticed, in lkml the discussion went into flames,
> fogetting the important points.
> [As this flame is going forgetting kbuild-2.5..]]
No need for a huge long e-mail to make a basic point:
Don't lump CML2 and Keith's kbuild work together.
I agree, and this is a good point.
> Tell us what is wrong in kbuild-2-5 and in CML2. Don't flame!
We've been doing that for CML2. For months, actually.
kbuild (again, as you point out) is quite another matter. Perhaps we
can point Keith to post a test patch against 2.5.5-pre1, for us to
review and comment on?
I believe there are probably still some issues to resolve, but I would
love to see a better makefile system for 2.5.
Regards,
Jeff
--
Jeff Garzik | "Why is it that attractive girls like you
Building 1024 | always seem to have a boyfriend?"
MandrakeSoft | "Because I'm a nympho that owns a brewery?"
| - BBC TV show "Coupling"
next prev parent reply other threads:[~2002-02-16 9:16 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 [this message]
2002-02-16 9:18 ` kbuild [which is not only ...2] David Woodhouse
2002-02-16 10:06 ` 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=3C6E2355.AA514ECA@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=cate@dplanet.ch \
--cc=kaos@ocs.com.au \
--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