From: Tomas Szepe <szepe@pinerecords.com>
To: Larry McVoy <lm@work.bitmover.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Larry McVoy <lm@bitmover.com>, 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 18:04:20 +0100 [thread overview]
Message-ID: <20030214170420.GD200@louise.pinerecords.com> (raw)
In-Reply-To: <20030214163611.GD3188@work.bitmover.com>
> [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?
What you have arranged for with Linus[1] using BK[2] is so contro-
versial that you must have expected to get A LOT of shit thrown at
you in the process, regardless of how much good/evil your work would
have caused. I'd expect that by now you would have long learnt
to completely ignore all the nonconstructive posts in the never-ending
BK threads and only focus on resolving technical problems.
[1] As one of the few symbols of the open source world.
[2] As proprietary software with lots of strings attached.
> I haven't noticed you, Alan, taking a half decade off to code up an SCM
> system good enough for Linus to use.
Alan's qualities are elsewhere, I'm sure you've noticed.
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-02-14 16:54 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 [this message]
2003-02-14 17:12 ` Larry McVoy
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=20030214170420.GD200@louise.pinerecords.com \
--to=szepe@pinerecords.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=lm@bitmover.com \
--cc=lm@work.bitmover.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