public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: Andi Kleen <ak@suse.de>
Cc: Pete Zaitcev <zaitcev@metabyte.com>, linux-kernel@vger.kernel.org
Subject: Re: So, what about kwhich on RH6.2?
Date: Thu, 04 Jan 2001 19:24:14 +1100	[thread overview]
Message-ID: <3A54332E.58374060@uow.edu.au> (raw)
In-Reply-To: <3A541361.65942CB3@metabyte.com> <3A5430C6.FBAB094A@uow.edu.au>, <3A5430C6.FBAB094A@uow.edu.au>; from andrewm@uow.edu.au on Thu, Jan 04, 2001 at 07:13:58PM +1100 <20010104091241.B18973@gruyere.muc.suse.de>

Andi Kleen wrote:
> 
> On Thu, Jan 04, 2001 at 07:13:58PM +1100, Andrew Morton wrote:
> > Silly question:
> >
> > can't we just hardwire `kgcc' into the build system and be done
> > with all this kwhich stuff?  It's just a symlink....
> 
> And break compilation on all non RedHat 7, non connectiva systems ?

I don't buy that.  The compulsory modutils upgrade a couple of months
back caused, what?  Ten emails?

> Would you volunteer to handle the support load on l-k that would cause?

With pleasure.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-04  8:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-04  6:08 So, what about kwhich on RH6.2? Pete Zaitcev
2001-01-04  6:11 ` David S. Miller
2001-01-04  7:07   ` Pete Zaitcev
2001-01-04  8:13 ` Andrew Morton
2001-01-04  8:12   ` Andi Kleen
2001-01-04  8:24     ` Andrew Morton [this message]
2001-01-04 14:42       ` Alan Cox
2001-01-04 14:41     ` Alan Cox
2001-01-04 22:03       ` J . A . Magallon
2001-01-04 22:12       ` Albert D. Cahalan
2001-01-05 10:57         ` Mike A. Harris

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=3A54332E.58374060@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@metabyte.com \
    /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