From: Krzysztof Halasa <khc@pm.waw.pl>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: New 'Changes-licensed-under' tag introduced for Linux-wireless
Date: Thu, 27 Sep 2007 22:17:43 +0200 [thread overview]
Message-ID: <m34phfsw0o.fsf@maximus.localdomain> (raw)
In-Reply-To: <20070927110950.0561eca1@freepuppy.rosehill> (Stephen Hemminger's message of "Thu, 27 Sep 2007 11:09:50 -0700")
Stephen Hemminger <shemminger@linux-foundation.org> writes:
> No, please don't down this legal rat hole. It would cause bullshit like
> people submitting dual licensed patches to the scheduler or GPL only
> patches to the ath5k or ACPI code.
Precisely. Signed-off-by means the patch author already authorized
the patch to be applied. With the patch merged the conditions still
in the file (project etc) apply and not some obscure email tags.
If someone really wants to change licencing conditions then the
licence conditions in the source code must be changed.
> Instead, add a section to Documentation/SubmittingPatches that clearly
> states that all changes to a file are licensed under the same license
> as the original file. I don't feel legally qualified to write the correct
> wording.
Current Documentation/SubmittingPatches:
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
indicated in the file; or
^^^^^^^^^^^^^^^^^^^^^
--
Krzysztof Halasa
next prev parent reply other threads:[~2007-09-27 20:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-27 18:00 New 'Changes-licensed-under' tag introduced for Linux-wireless Luis R. Rodriguez
2007-09-27 18:09 ` Stephen Hemminger
2007-09-27 20:17 ` Krzysztof Halasa [this message]
2007-09-27 18:54 ` Alexey Dobriyan
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=m34phfsw0o.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=shemminger@linux-foundation.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