All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn <core@enodev.com>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: Larry McVoy <lm@bitmover.com>,
	Diego Calleja Garc?a <diegocg@teleline.es>,
	Michael Bernstein <michael@seven-angels.net>,
	gmicsko@szintezis.hu, LKML <linux-kernel@vger.kernel.org>
Subject: Re: SCO offers UnixWare licenses for Linux
Date: 24 Jul 2003 12:46:33 -0500	[thread overview]
Message-ID: <1059068793.5082.3.camel@localhost> (raw)
In-Reply-To: <1059068046.577.3.camel@teapot.felipe-alfaro.com>

Joe coder cannot reasonably "check" anyway, and therefore cannot be held
liable. Only those with access to someone else's IP can reasonably be
held liable.

I really think that even though this thread is meta-relevant, it should
die now. No one has any relevant input.

On Thu, 2003-07-24 at 12:34, Felipe Alfaro Solana wrote:
> On Thu, 2003-07-24 at 17:08, Larry McVoy wrote:
> 
> > There seems to be a prevailing opinion that if there is stolen code in
> > Linux that came from SCO owned code that all that needs to be done is
> > to remove it and everything is fine.  I don't think it works that way.
> > If code was stolen and the fact that it is in Linux helped destroy
> > SCO's business then SCO has the right to try and get damages.  I.e.,
> > Linux damaged SCO by using the code.
> 
> I see the point but... Take Linux as a community. Let's say someone
> contributes stolen code, but the community doesn't check if the
> contributed code violates any IP or copyright law. So, is the Linux
> community guilty? Or else should the one that contributed code be
> considered guilty?
> 
> We can't be liable for the work of others over which we don't have total
> control. Or is the law forcing us to check line by line the
> contributions made by hundreds of programmers all around the world?

  reply	other threads:[~2003-07-24 17:31 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-21 17:10 SCO offers UnixWare licenses for Linux Gabor MICSKO
2003-07-21 17:52 ` Michael Bernstein
2003-07-21 18:59   ` Diego Calleja García
2003-07-21 20:09     ` Richard B. Johnson
2003-07-21 20:36       ` Shawn
2003-07-24 14:52     ` Felipe Alfaro Solana
2003-07-24 15:08       ` Larry McVoy
2003-07-24 15:49         ` Sancar Saran
2003-07-24 19:32           ` Alan Cox
2003-07-25 11:44             ` Sancar Saran
2003-07-24 15:54         ` Richard B. Johnson
2003-07-24 16:01           ` Larry McVoy
2003-07-24 16:17             ` Tomas Szepe
2003-07-24 16:39             ` Yuliy Pisetsky
2003-07-24 16:55               ` Larry McVoy
2003-07-24 18:48                 ` nick
2003-07-24 16:52             ` Ian Hastie
2003-07-24 17:22               ` Larry McVoy
2003-07-24 22:52                 ` Stephan von Krawczynski
2003-07-24 17:00             ` David Benfell
2003-07-24 17:34         ` Felipe Alfaro Solana
2003-07-24 17:46           ` Shawn [this message]
2003-07-24 22:55           ` Jan Harkes
2003-07-24 23:27           ` Stephan von Krawczynski
2003-07-25 19:29           ` Timothy Miller
2003-07-24 21:03         ` Leandro Guimarães Faria Corsetti Dutra
2003-07-21 17:53 ` Jeff Sipek
2003-07-21 22:35   ` Brian McGroarty
2003-07-22 19:48     ` Jamie Lokier
2003-07-22  3:41 ` Kurt Wall
2003-07-21 17:24 Mudama, Eric
2003-07-22 23:34 Clayton Weaver
     [not found] <20030724234213.GA20064@work.bitmover.com>
2003-07-25  0:11 ` Michael Bernstein
2003-07-25  0:21   ` Larry McVoy
2003-07-25 12:43     ` Jamie Lokier
2003-07-25 13:37       ` David S. Miller
2003-07-25 15:09         ` Yaroslav Rastrigin
2003-07-25 15:10           ` David S. Miller
2003-07-25 15:17           ` Larry McVoy
2003-07-25 13:37 Downing, Thomas
2003-07-26  8:21 Anuradha Ratnaweera
2003-07-26 14:49 ` Henrik Persson

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=1059068793.5082.3.camel@localhost \
    --to=core@enodev.com \
    --cc=diegocg@teleline.es \
    --cc=felipe_alfaro@linuxmail.org \
    --cc=gmicsko@szintezis.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=michael@seven-angels.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.