The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: 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 08:36:11 -0800	[thread overview]
Message-ID: <20030214163611.GD3188@work.bitmover.com> (raw)
In-Reply-To: <1045243414.1353.28.camel@irongate.swansea.linux.org.uk>

On Fri, Feb 14, 2003 at 05:23:35PM +0000, Alan Cox wrote:
> And no I don't want to use bitkeeper any more, your ever changing
> licenses and removals of more and more rights have reminded me why 
> many proprietary vendors just cannot be trusted and why format lockin
> is so dangerous.

The license hasn't changed in almost a year, so perhaps you'd care to 
back up this "ever changing licenses" statement with some data?  Stop
spreading FUD, Alan, it's beneath you.  I could just as easily attack
Red Hat for getting patents, do you see me doing that?  

And just what rights have we removed?  Since the license hasn't changed,
it's sort of hard to say that the rights have changed.  More FUD.

And what format lockin?  It's an open format, GNU CSSC reads and writes
it just fine, and we've made a point over the years of telling them each
time we change something so that they can continue to read/write our
files.  More FUD.

> You are turning a simple "can I have that in a format I can read" into 
> yet another epic bitkeeper flame war.

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.  I haven't noticed you, Alan,
taking a half decade off to code up an SCM system good enough for
Linus to use.  Without the benefit of having one to copy, by the way.
When you've done that you are welcome to critize how I went about it.
Until then, stop your whining.
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  reply	other threads:[~2003-02-14 16:26 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 [this message]
2003-02-14 17:04             ` Tomas Szepe
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=20030214163611.GD3188@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 \
    /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