All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/5] docs/manual: slightly clarify patch licensing
Date: Wed, 3 Feb 2016 23:53:44 +0100	[thread overview]
Message-ID: <20160203225344.GA3428@free.fr> (raw)
In-Reply-To: <1454365196-26319-3-git-send-email-luca@lucaceresoli.net>

Luca, All,

On 2016-02-01 23:19 +0100, Luca Ceresoli spake thusly:
> 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>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

Regards,
Yann E. MORIN.

> ---
> Changes v1 -> v2:
> - "they modify" -> "they apply to" (Thomas).
> ---
>  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..d50c971 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 they apply
> +to.
>  
>  A message explaining what the patch does, and why it is needed, should
>  be added in the header commentary of the patch.
> -- 
> 1.9.1
> 

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2016-02-03 22:53 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01 22:19 [Buildroot] [PATCH v2 0/5] Patch file clarification & Co Luca Ceresoli
2016-02-01 22:19 ` [Buildroot] [PATCH v2 1/5] Update copyright year Luca Ceresoli
2016-02-01 22:24   ` Luca Ceresoli
2016-02-01 22:19 ` [Buildroot] [PATCH v2 2/5] docs/manual: slightly clarify patch licensing Luca Ceresoli
2016-02-02  8:58   ` Yann E. MORIN
2016-02-03 22:53   ` Yann E. MORIN [this message]
2016-02-10 22:15   ` Arnout Vandecappelle
2016-02-25 10:50   ` Peter Korsgaard
2016-02-01 22:19 ` [Buildroot] [PATCH v2 3/5] COPYING: add exception about " Luca Ceresoli
2016-02-01 22:31   ` Thomas Petazzoni
2016-02-03 23:02   ` Yann E. MORIN
2016-02-03 23:57     ` Arnout Vandecappelle
2016-02-04 20:42       ` Yann E. MORIN
2016-02-04 21:08         ` Thomas Petazzoni
2016-02-04 21:40           ` Yann E. MORIN
2016-02-04 21:51             ` Thomas Petazzoni
2016-02-04 22:28               ` Steve Calfee
2016-02-05  9:25         ` Luca Ceresoli
2016-02-05 12:07           ` Peter Korsgaard
2016-02-10 22:35     ` Arnout Vandecappelle
2016-02-19 17:28       ` Luca Ceresoli
2016-02-25 10:57         ` Peter Korsgaard
2016-02-25 11:53           ` Luca Ceresoli
2016-02-01 22:19 ` [Buildroot] [PATCH v2 4/5] docs/manual: add section " Luca Ceresoli
2016-02-03 23:34   ` Yann E. MORIN
2016-02-26 22:08     ` Luca Ceresoli
2016-02-26 22:28       ` Yann E. MORIN
2016-02-10 22:37   ` Arnout Vandecappelle
2016-02-01 22:19 ` [Buildroot] [PATCH v2 5/5] legal-info: explicitly state how patches are licensed Luca Ceresoli
2016-03-06 15:14   ` Thomas Petazzoni
2016-03-06 22:52     ` Luca Ceresoli
2016-03-06 22:56       ` 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=20160203225344.GA3428@free.fr \
    --to=yann.morin.1998@free.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.