linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jw schultz <jw@pegasys.ws>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: The Well-Factored 386
Date: Mon, 28 Jul 2003 20:49:41 -0700	[thread overview]
Message-ID: <20030729034941.GA14812@work.bitmover.com> (raw)
In-Reply-To: <1059442052.1869.11.camel@dhcp22.swansea.linux.org.uk>

On Tue, Jul 29, 2003 at 02:27:32AM +0100, Alan Cox wrote:
> On Maw, 2003-07-29 at 01:34, jw schultz wrote:
> > Now if we could cut off the threads about BK (as opposed to
> > bk servers) started by anyone other than Larry...
> 
> Even better - by Larry too, excepting when its kernel relevant like
> downtimes, updates etc

Dave and Linus cc-ed me on the vger crackdown discussions and I offered 
to unsubscribe from the kernel list if it would help.  Dave's comment was
that I don't start the wars, which is probably true.  I tend to respond
to attacks, not go looking for fights.  I'd be curious to know when it is
that you think I've started a flame fest here, Alan.

I'm here for two reasons, I like OS topics and I want to support BK.
That latter one is a problem, the same character traits which make
me want to help people when they have problems are the ones that make
me participate in the BK flames.  If the kernel community is ready to
operate on a lower level of support from us, I'll bow out.  It hasn't
been pleasant being here for the last couple of years and I'd prefer 
to be gone.
-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm

  reply	other threads:[~2003-07-29  3:49 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
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 [this message]
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=20030729034941.GA14812@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jw@pegasys.ws \
    --cc=linux-kernel@vger.kernel.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).