From: Jeff.Haran@citrix.com (Jeff Haran)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel contributions from organisations and individual privacy
Date: Mon, 15 Jun 2015 23:08:36 +0000 [thread overview]
Message-ID: <4E5779AD88B2F040B8A7E83ECF544D1A603B3B@SJCPEX01CL03.citrite.net> (raw)
In-Reply-To: <87381vmxb0.fsf@nemi.mork.no>
> -----Original Message-----
> From: Bj?rn Mork [mailto:bjorn at mork.no]
> Sent: Saturday, June 13, 2015 8:40 AM
> To: Jeff Haran
> Cc: Rik van Riel; kernelnewbies at kernelnewbies.org
> Subject: Re: Kernel contributions from organisations and individual privacy
>
> Jeff Haran <Jeff.Haran@citrix.com> writes:
>
> > What is the downside to a large company for violating GPL?
>
> Losing all rights to the software in question forever is probably the largest
> downside. If we talk about the Linux kernel (as I assume we do in this forum)
> then I have a hard time believing any company can survive that.
Has this ever actually happened?
Specifically has a company that violated Linux's GPL ever been sued over the violation, lost the case and as a result lost the ability to use the Linux kernel forever?
Thanks,
Jeff Haran
next prev parent reply other threads:[~2015-06-15 23:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 9:19 Kernel contributions from organisations and individual privacy Chris Packham
2015-06-11 4:58 ` Jason Ball
2015-06-11 5:10 ` Chris Packham
2015-06-11 5:19 ` Ruben Safir
2015-06-11 14:28 ` Greg KH
2015-06-11 14:41 ` Ruben Safir
2015-06-11 15:38 ` Greg KH
2015-06-11 16:39 ` Ruben Safir
2015-06-11 17:54 ` Greg KH
2015-06-11 17:57 ` Greg KH
2015-06-11 23:26 ` Ruben Safir
2015-06-11 23:37 ` Rik van Riel
2015-06-11 23:55 ` Ruben Safir
2015-06-12 0:13 ` Jeff Haran
2015-06-12 1:28 ` Rik van Riel
2015-06-12 23:29 ` Jeff Haran
2015-06-13 15:40 ` Bjørn Mork
2015-06-13 19:08 ` Ruben Safir
2015-06-15 23:08 ` Jeff Haran [this message]
2015-06-15 23:55 ` Rik van Riel
2015-06-16 16:23 ` Jeff Haran
2015-06-13 16:23 ` Rik van Riel
2015-06-14 21:18 ` Valdis.Kletnieks at vt.edu
[not found] ` <B424B28F-AB7E-4972-95BB-FF91D85D0FED@gmail.com>
2015-06-14 23:29 ` Valdis.Kletnieks at vt.edu
[not found] ` <557E0FF7.1000607@gmail.com>
2015-06-15 2:08 ` Valdis.Kletnieks at vt.edu
2015-06-12 0:52 ` Greg KH
2015-06-12 3:31 ` Valdis.Kletnieks at vt.edu
2015-06-12 4:39 ` Ruben Safir
2015-06-12 7:18 ` Valdis.Kletnieks at vt.edu
2015-06-11 13:13 ` Rik van Riel
2015-06-11 14:27 ` Greg KH
2015-06-11 14:25 ` Greg KH
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=4E5779AD88B2F040B8A7E83ECF544D1A603B3B@SJCPEX01CL03.citrite.net \
--to=jeff.haran@citrix.com \
--cc=kernelnewbies@lists.kernelnewbies.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 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.