linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: "David S. Miller" <davem@redhat.com>
Cc: rickh@capaccess.org, linux-kernel@vger.kernel.org,
	linux-assembly@vger.kernel.org
Subject: Re: The Well-Factored 386
Date: Tue, 29 Jul 2003 00:27:37 +0200	[thread overview]
Message-ID: <20030729002737.111bc3ad.skraw@ithnet.com> (raw)
In-Reply-To: <20030728133300.2ef96cf4.davem@redhat.com>

On Mon, 28 Jul 2003 13:33:00 -0700
"David S. Miller" <davem@redhat.com> wrote:

> On Mon, 28 Jul 2003 16:33:58 -0400
> "Rick A. Hohensee" <rickh@capaccess.org> wrote:
> 
> > Rick Hohensee   July 2003
> > 
> > Why, Rick? WHY?
> 
> Rick, I wish you luck finding another machine with lists to
> infiltrate.
> 
> Because you're not going to do it on vger.kernel.org any more.
> Bye bye.

Dave, I have to tell you I don't like your attitude shown in this case. Surely
you can argue Rick does not really stay on a specific topic, but on the other
hand he does not really flood the list, does he? I mean, compared to (name
deleted)s' PR bubbles he is really low volume.
Besides I have not read any complaints (1 pro) - only yours. Which leads me to
think you kill him only because you don't like the man - and not really because
of his writing - and because you _can_. This does not feel alright for me.
Don't get me wrong, I am no Rick-fan, I don't know him and have no idea why he
is really talking about his favourite topics. But I honour his right to speak
up just like anybody else, even if it looks more like a "brainstorming" than
constructive talking.

Regards,
Stephan


  reply	other threads:[~2003-07-28 22:27 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-28  8:44 The Well-Factored 386 Rick A. Hohensee
2003-07-28 14:06 ` David S. Miller
2003-07-28 16:36   ` hp
2003-07-28 20:33   ` Rick A. Hohensee
2003-07-28 20:33     ` David S. Miller
2003-07-28 22:27       ` Stephan von Krawczynski [this message]
2003-07-28 22:30         ` David S. Miller
2003-07-28 22:58           ` David D. Hagood
2003-07-29 14:32             ` Timothy Miller
2003-07-29 17:21               ` hp
2003-07-29  0:34           ` jw schultz
2003-07-29  1:27             ` Alan Cox
2003-07-29  3:49               ` Larry McVoy
2003-07-29  4:25                 ` Gene Heskett
2003-07-29  4:42                 ` jw schultz
2003-07-29 12:04                 ` Alan Cox
2003-07-29 14:55                 ` Timothy Miller
2003-07-29  8:45           ` hp
2003-07-28 23:11         ` viro
2003-07-29  0:17       ` Brian Raiter
2003-07-28 16:02 The well-factored 386 Jack Dennon
2003-07-28 16:32 ` David S. Miller
2003-07-28 16:46   ` Andries Brouwer
2003-07-28 16:55     ` David S. Miller
2003-07-28 19:31       ` Herbert Pötzl
2003-07-28 19:41   ` Jamie Lokier
2003-07-29 11:14     ` Helge Hafting
2003-07-29 16:19       ` Jamie Lokier
2003-07-30  7:11         ` Helge Hafting
2003-07-30 14:05           ` Jamie Lokier
2003-07-29 12:59 John Bradford
2003-07-29 13:32 ` Ville Herva

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=20030729002737.111bc3ad.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=davem@redhat.com \
    --cc=linux-assembly@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rickh@capaccess.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;
as well as URLs for NNTP newsgroup(s).