From: Mark Mielke <mark@mark.mielke.cc>
To: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
Cc: Kai Henningsen <kaih@khms.westfalen.de>, linux-kernel@vger.kernel.org
Subject: Re: If you want kbuild 2.5, tell Linus
Date: Thu, 6 Jun 2002 21:39:35 -0400 [thread overview]
Message-ID: <20020606213935.B3551@mark.mielke.cc> (raw)
In-Reply-To: <200206062101.QAA15457@tomcat.admin.navo.hpc.mil>
On Thu, Jun 06, 2002 at 04:01:27PM -0500, Jesse Pollard wrote:
> kaih@khms.westfalen.de (Kai Henningsen):
> > Frankly, I see *absolutely no way* how the current Kai-Linus "merge" can
> > possibly end with something even remotely like Keith's kbuild2.5. Unless
> > Linus changes his approach radically.
> > If I were Keith, I'd be rather upset, too.
> How about the following approach, which MAY not be practical:
> 1. Name all of the new Makefiles Makefile.k2.5
> 2. Create a small wrapper script to define make as "make -f Makefile.k2.5"
> or just define MAKE as make -f Makefile.k2.5 in the top level
> Makefile.k2.5
I think if you had read their posts more thoroughly, or checked the patch
out yourself, you would have found that they already did this.
kbuild2.5 and kbuild2.4 are already made to exist side by side.
I dunno about the Linus-wall thing though. I think Linus has good reasons
that apply in the general case, but probably don't apply at all for this
specific case.
How do you make an exception without allowing for exceptions?
mark
--
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
next prev parent reply other threads:[~2002-06-07 1:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 21:01 If you want kbuild 2.5, tell Linus Jesse Pollard
2002-06-06 21:36 ` Tomas Szepe
2002-06-10 21:43 ` Bill Davidsen
2002-06-07 1:39 ` Mark Mielke [this message]
2002-06-07 15:31 ` Thunder from the hill
2002-06-08 15:51 ` David Woodhouse
2002-06-08 15:54 ` Thunder from the hill
-- strict thread matches above, loose matches on Subject: below --
2002-06-04 7:04 Martin.Knoblauch
2002-06-03 17:33 Martin.Knoblauch
2002-06-03 17:48 ` Thunder from the hill
2002-06-03 15:29 Wayne.Brown
2002-06-03 16:05 ` Mark Mielke
2002-06-03 17:24 ` Thunder from the hill
2002-06-03 13:58 Keith Owens
2002-06-03 13:20 ` Martin Dalecki
2002-06-03 14:36 ` Tomas Szepe
2002-06-03 14:15 ` Daniel Phillips
2002-06-03 17:51 ` Austin Gonyou
2002-06-03 22:10 ` Diego Calleja
2002-06-03 22:24 ` John Alvord
2002-06-03 22:34 ` Thunder from the hill
2002-06-03 23:10 ` Diego Calleja
2002-06-04 1:26 ` Daniel Phillips
2002-06-06 19:31 ` Kai Henningsen
2002-06-06 20:56 ` Tom Rini
2002-06-07 0:30 ` Daniel Phillips
2002-06-07 15:29 ` Thunder from the hill
2002-06-03 14:33 ` Nicolas Pitre
2002-06-03 15:27 ` Peter Wächtler
2002-06-03 16:09 ` Nicolas Pitre
2002-06-03 14:54 ` Daniel Phillips
2002-06-03 17:26 ` Olivier Galibert
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=20020606213935.B3551@mark.mielke.cc \
--to=mark@mark.mielke.cc \
--cc=kaih@khms.westfalen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pollard@tomcat.admin.navo.hpc.mil \
/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