public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kaih@khms.westfalen.de (Kai Henningsen)
To: torvalds@transmeta.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] /proc/sys/kernel/pointer_size
Date: 11 Jan 2003 11:18:00 +0200	[thread overview]
Message-ID: <8deE8FwHw-B@khms.westfalen.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0301081300200.1497-100000@home.transmeta.com>

torvalds@transmeta.com (Linus Torvalds)  wrote on 08.01.03 in <Pine.LNX.4.44.0301081300200.1497-100000@home.transmeta.com>:

> On Wed, 8 Jan 2003, John Levon wrote:
> > On Wed, Jan 08, 2003 at 12:28:23PM -0800, Linus Torvalds wrote:

> > > or could even be a user program config file option.
> >
> > Eww.
>
> And it's less disgusting than adding a kernel hack for it?

>From my point of view as both user and programmer: about a hundred times  
less disgusting. (Also probably needs at least ten (maybe a hundred) times  
less code, including the kernel code, which plays a big part in the  
"disgusting" value.)

MfG Kai

  parent reply	other threads:[~2003-01-11 11:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 19:59 [PATCH] /proc/sys/kernel/pointer_size John Levon
2003-01-08 20:28 ` Linus Torvalds
2003-01-08 20:52   ` John Levon
2003-01-08 21:03     ` Linus Torvalds
2003-01-08 22:37       ` David S. Miller
2003-01-08 22:40       ` John Levon
2003-01-11  9:18       ` Kai Henningsen [this message]
2003-01-08 22:34   ` David S. Miller
2003-01-08 23:04     ` Linus Torvalds
2003-01-08 23:03       ` David S. Miller
2003-01-09  0:02         ` Linus Torvalds
2003-01-09  0:03           ` David S. Miller
2003-01-09  4:00             ` Daniel Jacobowitz
2003-01-09  4:31               ` David S. Miller
2003-01-09  5:23               ` William Lee Irwin III
2003-01-09 23:09       ` Bill Davidsen

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=8deE8FwHw-B@khms.westfalen.de \
    --to=kaih@khms.westfalen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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