From: Larry McVoy <lm@bitmover.com>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: Larry McVoy <lm@bitmover.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
David Dillow <dillowd@y12.doe.gov>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-net@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: 3Com 3cr990 driver release
Date: Fri, 14 Feb 2003 09:12:19 -0800 [thread overview]
Message-ID: <20030214171219.GB6564@work.bitmover.com> (raw)
In-Reply-To: <20030214170420.GD200@louise.pinerecords.com>
On Fri, Feb 14, 2003 at 06:04:20PM +0100, Tomas Szepe wrote:
> > [lm@bitmover.com]
> >
> > No, I'm countering a pile of pathetic FUD from someone who has no
> > business spreading it. I've taken a lot of crap in return for helping
> > the kernel effort and I'm sick of it.
>
> Look, I don't want this to sound harsh, but what did you expect?
I had the naive expectation that having been around in the kernel
community for a long time, and having never done anything except attempt
to continue to help, that maybe people would wait until some wrong took
place before starting with the mud slinging.
Silly me, what was I thinking?
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-02-14 17:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 7:50 3Com 3cr990 driver release David Dillow
2003-02-14 8:20 ` Jeff Garzik
2003-02-14 14:33 ` Alan Cox
2003-02-14 15:19 ` Larry McVoy
2003-02-14 16:54 ` Alan Cox
2003-02-14 16:09 ` Larry McVoy
2003-02-14 17:23 ` Alan Cox
2003-02-14 16:36 ` Larry McVoy
2003-02-14 17:04 ` Tomas Szepe
2003-02-14 17:12 ` Larry McVoy [this message]
2003-02-14 18:40 ` Roman Zippel
2003-02-14 18:44 ` Larry McVoy
2003-02-14 18:59 ` Roman Zippel
2003-02-15 11:34 ` Henning P. Schmiedehausen
2003-02-14 17:28 ` Alan Cox
2003-02-14 23:01 ` Steven Cole
2003-02-14 17:20 ` David Dillow
2003-02-14 20:52 ` Alan Cox
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=20030214171219.GB6564@work.bitmover.com \
--to=lm@bitmover.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dillowd@y12.doe.gov \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=szepe@pinerecords.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