From: Russell King <rmk@arm.linux.org.uk>
To: Balbir Singh <balbir_soni@yahoo.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Patches have a license
Date: Mon, 27 Jan 2003 12:03:34 +0000 [thread overview]
Message-ID: <20030127120334.A28375@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030127095840.25042.qmail@web13601.mail.yahoo.com>; from balbir_soni@yahoo.com on Mon, Jan 27, 2003 at 01:58:40AM -0800
On Mon, Jan 27, 2003 at 01:58:40AM -0800, Balbir Singh wrote:
> Looking at the recent posting on lkml, I find that
> a lot of people tend to take and apply patches posted
> on lkml into proprietary modules.
There are two ways to look at a patch on a public mailing list such as
LKML - either it is a public publication without restriction, or it
is a derived work of a copyrighted work, where the copyright on that
work explicitly covers derived works. I'm not going to argue which
since that's the domain of legal people to sort out, and one that I'm
not particularly interested in.
However, basic common sense suggests that if a patch author wants to
ensure that patches are not used in a way that they do not intend them
to be used, then the patch author should explicitly state the license
that they supply the patches under.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-01-27 11:54 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
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 [this message]
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=20030127120334.A28375@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=balbir_soni@yahoo.com \
--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