Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/5] docs/manual: slightly clarify patch licensing
Date: Mon, 1 Feb 2016 19:57:40 +0100	[thread overview]
Message-ID: <56AFAAA4.6050908@lucaceresoli.net> (raw)
In-Reply-To: <20160201195312.09e2d34f@free-electrons.com>

Hi Thomas,

Thomas Petazzoni wrote:
> Luca,
>
> On Mon,  1 Feb 2016 15:52:21 +0100, Luca Ceresoli wrote:
>> Adding a patch is a modification to Buildroot. Thus this sentence might be
>> interpreted as "Patches are released under the Buildroot license".
>>
>> Being a legal matter, the last thing we want is to be
>> ambiguous. Reword the sentence to avoid any misunderstandings.
>>
>> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
>> ---
>>   docs/manual/patch-policy.txt | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/docs/manual/patch-policy.txt b/docs/manual/patch-policy.txt
>> index 0b4604e..cfda5c5 100644
>> --- a/docs/manual/patch-policy.txt
>> +++ b/docs/manual/patch-policy.txt
>> @@ -90,8 +90,8 @@ If something goes wrong in the steps _3_ or _4_, then the build fails.
>>
>>   === Format and licensing of the package patches
>>
>> -Patches are released under the same license as the software that is
>> -modified.
>> +Patches are released under the same license as the software that they
>> +modify.
>
> "as the software that they apply to" ?

Indeed, they don't modify any file, `patch` does it! :)

Seriously, your version is better. We can even ditch "that":
"as the software they apply to".

Will fix and resend.

-- 
Luca

  reply	other threads:[~2016-02-01 18:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01 14:52 [Buildroot] [PATCH 0/5] Patch file clarification & Co Luca Ceresoli
2016-02-01 14:52 ` [Buildroot] [PATCH 1/5] Update copyright year Luca Ceresoli
2016-02-01 14:52 ` [Buildroot] [PATCH 2/5] docs/manual: slightly clarify patch licensing Luca Ceresoli
2016-02-01 18:53   ` Thomas Petazzoni
2016-02-01 18:57     ` Luca Ceresoli [this message]
2016-02-01 14:52 ` [Buildroot] [PATCH 3/5] COPYING: add exception about " Luca Ceresoli
2016-02-01 18:54   ` Thomas Petazzoni
2016-02-01 14:52 ` [Buildroot] [PATCH 4/5] docs/manual: add section " Luca Ceresoli
2016-02-01 18:55   ` Thomas Petazzoni
2016-02-01 22:12     ` Luca Ceresoli
2016-02-01 14:52 ` [Buildroot] [PATCH 5/5] legal-info: explicitly state how patches are licensed Luca Ceresoli
2016-02-01 18:55   ` Thomas Petazzoni
2016-02-01 20:21   ` Yann E. MORIN

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=56AFAAA4.6050908@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --cc=buildroot@busybox.net \
    /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