From: John Bradford <john@grabjohn.com>
To: davej@codemonkey.org.uk (Dave Jones)
Cc: balbir_soni@yahoo.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Patches have a license
Date: Mon, 27 Jan 2003 11:10:25 +0000 (GMT) [thread overview]
Message-ID: <200301271110.h0RBAPLq000352@darkstar.example.net> (raw)
In-Reply-To: <20030127104705.GC25913@codemonkey.org.uk> from "Dave Jones" at Jan 27, 2003 10:47:05 AM
> > I would request everyone to post their patches with
> > a license, failing which it should be assumed that
> > the license is GPL.
>
> Surely the license of the diff matches the license of the
> code it is patching ?
That is what I've always thought. However, in any case, even if the
patch itself isn't explicitly licensed as GPL, the code generated as a
result of patching a GPLed piece of code, must surely be GPLed,
because applying the patch is no different to editing the file with a
text editor.
John.
next prev parent reply other threads:[~2003-01-27 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 9:58 [RFC] Patches have a license Balbir Singh
2003-01-27 10:47 ` Dave Jones
2003-01-27 11:10 ` John Bradford [this message]
2003-01-27 11:30 ` Andre Hedrick
2003-01-27 11:34 ` Sean Neakums
2003-01-27 11:47 ` Helge Hafting
2003-01-27 20:04 ` dean gaudet
2003-01-27 12:03 ` Russell King
2003-01-27 12:12 ` Andre Hedrick
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=200301271110.h0RBAPLq000352@darkstar.example.net \
--to=john@grabjohn.com \
--cc=balbir_soni@yahoo.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@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