Re: Do I have to release the patch for a GPL software under GPL?

[Bernd Jendrissek]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In article <mailman.1491.1146854152.9609.gnu-misc-discuss@gnu.org>
Dancefire <dancefire@gmail.com> wrote:
>I am confusing on GPL now, I need someone to clear me.

Or maybe you're not confused, but just unhappy that it doesn't condone
your desire to take away some of your customers' freedoms.

>Do I have to release the patch under GPL if the patch is for a GPL
>software?  As my understanding, for example, If I modified Linux
>kernel, I do not have to release it under GPL if I use it privately,
>unless I make it public. But how about the patch for the kernel? That
>is, if I generate the patch of my modification for the Linux Kernel,
>and never release the modified Linux kernel to public, however, I want
>to sell the kernel patch of the Linux to customers as whatever license
>as I want, but I don?t want the patch under GPL for some reason. Can I?

Your customers will have to apply the patch themselves.  If you give
them an already patched kernel, you will have to release it to them with
the GPL (modulo BSD-type parts of the kernel) covering the *whole*
derived work, otherwise your redistribution will be in violation of the
only licence you have to redistribute, the GPL (module BSDish and public
domain parts).

IANAL BTW.

- -- 
"If you lie to the compiler, it will get its revenge." - Henry Spencer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Please fetch my new key 804177F8 from hkp://wwwkeys.eu.pgp.net/

iD8DBQFEW8F/wyMv24BBd/gRAhRrAKCTpbSQ26Ep8nQ9+Vf42yGkFS76jACfQc9x
DE538E2WZMAE7w/gj9Dv5Tw=
=+ie8
-----END PGP SIGNATURE-----