linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mats Liljegren <liljegren.mats2@gmail.com>
To: Rogelio Serrano <rogelio.serrano@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>,
	"luke.leighton" <luke.leighton@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Transcend's "one of the most cavalier GPL violations in a long time"
Date: Tue, 15 Oct 2013 09:48:49 +0200	[thread overview]
Message-ID: <CA+xJJ19v4hD0VX3g2qwGLAZax=ssW7YPdumK25vpGs=3eebCEg@mail.gmail.com> (raw)
In-Reply-To: <CANszf4gNGGTuTJjssmO5hntcKsCcJY7OG3VNTcDpm10SAMbevg@mail.gmail.com>

> I was led to believe this in the busybox list. maybe we are communally
> smoking the same stuff. Linux Kernel Developers would rather go on
> developing better code than waste time on enforcement. Some even think
> it is counter productive to adoption of linux.
>
> Transcend most likely knows this.
>
> You have a piece of code under the GPL and the majority of the
> copyright holders say they will not enforce it. Thats virtually public
> domain code. Thats why i stopped contributing to the linux kernel and
> opted to maintain a massive patch instead.

I think it is sad that you take this decision purely based on the fact
that by contributing to the Linux kernel you will not get help to
enforce the GPL license for your code.

I'm a little bit curious however: In what way do you now have better
ways to enforce the GPL license of your code now that you maintain a
massive patch? Is it that you never show it to the public?

  reply	other threads:[~2013-10-15  7:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACGw4H5+5bkgy+UJPCbwG2KXZDj3zhXLR4cZCbeDvjJhfTJwmQ@mail.gmail.com>
     [not found] ` <CAPweEDzf1DbRHeXr_cL8ZZk9s0Srhp0s5rrYm0pksyurO0CXpw@mail.gmail.com>
2013-09-20 11:29   ` Fwd: Transcend's "one of the most cavalier GPL violations in a long time" luke.leighton
2013-10-08 14:47     ` Pavel Machek
2013-10-08 16:08     ` Rogelio Serrano
2013-10-13 12:02       ` Pavel Machek
2013-10-15  6:42         ` Rogelio Serrano
2013-10-15  7:48           ` Mats Liljegren [this message]
2013-10-15 11:10           ` Pavel Machek
2013-10-28  0:28           ` Rob Landley

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='CA+xJJ19v4hD0VX3g2qwGLAZax=ssW7YPdumK25vpGs=3eebCEg@mail.gmail.com' \
    --to=liljegren.mats2@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke.leighton@gmail.com \
    --cc=pavel@ucw.cz \
    --cc=rogelio.serrano@gmail.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;
as well as URLs for NNTP newsgroup(s).