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:09:15 -0800	[thread overview]
Message-ID: <20030214160915.GC3188@work.bitmover.com> (raw)
In-Reply-To: <1045241640.1353.13.camel@irongate.swansea.linux.org.uk>

On Fri, Feb 14, 2003 at 04:54:01PM +0000, Alan Cox wrote:
> On Fri, 2003-02-14 at 15:19, Larry McVoy wrote:
> > > Would you care to make the patches available in a format those of us who
> > > work on open source version control systems can use. Right now Mr McVoy
> > > prohibits me from reviewing your patches.
> > 
> > That seems a bit extreme, Alan.  I don't recall prohibiting you from anything
> > of the kind.
> 
> 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.

I tend to doubt that you really want to use BK, you seem to have strong
feelings about it, but if you do and you want to be sure that you can,
that's an easily solved problem.  And if you don't want to be special
cased, which is understandable, then you can have a manager from Red Hat
talk to me and we'll work it out just like we're working it out with other
companies.

That goes for any other kernel developer who feels that they are in
a gray area.  No, we're not going to make an exception if you are 
actively contributing to a different SCM system, that's where we draw
the line.  But the license cast a wide net by saying "you or anyone in
your company" so we're willing to work out.  The goal is to support 
kernel development, and there is another unfortunate constraint of 
not shooting ourselves in the foot.  As long as we can do both, we 
will.
-- 
---
Larry McVoy            	 lm at bitmover.com           http://www.bitmover.com/lm 

  reply	other threads:[~2003-02-14 15:59 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 [this message]
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
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=20030214160915.GC3188@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