public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
Cc: linux-kernel@vger.kernel.org
Subject: Re: If you want kbuild 2.5, tell Linus
Date: Thu, 6 Jun 2002 23:36:29 +0200	[thread overview]
Message-ID: <20020606213628.GK17859@louise.pinerecords.com> (raw)
In-Reply-To: <200206062101.QAA15457@tomcat.admin.navo.hpc.mil>

> How about the following approach, which MAY not be practical:

Please note that there have already been innumerable proposals of
how to merge kbuild 2.5, and all of them have been silently rejected.

What I keep pondering over is, what is it that Linus finds troublesome
about merging the whole of kbuild 2.5? More -- why has he decided to
keep this to himself? Something tells me the answer to these questions
might be the key to solving the whole kb25 merge problem.

Hmmmm, it's rather odd to have to write about someone in 3rd person
when you know they'll read the text; They'll even give it a bit of
thought and will likely have things to say. They won't let you know,
though. You've noticed Linus was a he in the "if you want kbuild 2.5,
tell Linus" mail, haven't you? If I was a psychologist, I might have
something interesting to say based on that information. :)

Oh well.

And as for your idea, I'd say it really is impractical. kbuild 2.5
can live in perfect peace with the old build system as it is.

T.

  reply	other threads:[~2002-06-06 21:36 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 [this message]
2002-06-10 21:43   ` Bill Davidsen
2002-06-07  1:39 ` Mark Mielke
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=20020606213628.GK17859@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --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