mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Larry McVoy <lm@bitmover.com>
Cc: 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: 14 Feb 2003 17:23:35 +0000	[thread overview]
Message-ID: <1045243414.1353.28.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20030214160915.GC3188@work.bitmover.com>

On Fri, 2003-02-14 at 16:09, Larry McVoy wrote:
> > Since I work for a company who works on competing version control products I'm
> > not allowed to use bitkeeper. Since his patches are only in bitkeeper format
> > I can't read them.
> 
> Sure you can, unless your objection extends to getting at data which is in
> BK over the web.  http://typhoon.bkbits.net:8080/typhoon-2.4/patch@+
> 
> And you have options beyond that.  Perhaps it has escaped your notice that
> Dave M and others who are also employed by Red Hat are (happily?) using
> BK and we haven't kicked up a fuss.

Since Red Hat works on CVS I wonder if they are breaking the license or
not. However thats not relevant right now. If I get stuff in .doc format
that I can't read I ask people to resend it in a format I can, ditto
bitkeeper or any other randomly weird VC file.

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.

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

Alan


  reply	other threads:[~2003-02-14 16:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-14  7:50 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 [this message]
2003-02-14 16:36           ` Larry McVoy
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=1045243414.1353.28.camel@irongate.swansea.linux.org.uk \
    --to=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 \
    /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

all inboxes | Powered by JetHome®