Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/5] legal-info: explicitly state how patches are licensed
Date: Mon, 1 Feb 2016 21:21:09 +0100	[thread overview]
Message-ID: <20160201202109.GE4278@free.fr> (raw)
In-Reply-To: <1454338344-24973-6-git-send-email-luca@lucaceresoli.net>

Luca, All,

On 2016-02-01 15:52 +0100, Luca Ceresoli spake thusly:
> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>

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

Regards,
Yann E. MORIN.

> ---
>  support/legal-info/README.header | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/support/legal-info/README.header b/support/legal-info/README.header
> index 0b5aa66..316f799 100644
> --- a/support/legal-info/README.header
> +++ b/support/legal-info/README.header
> @@ -18,7 +18,7 @@ This material is composed of the following items.
>     sources/ subdirectory (except for the non-redistributable packages, which
>     have not been saved). Patches that were applied are also saved, along
>     with a file named 'series' that lists the patches in the order they were
> -   applied.
> +   applied. Patches are under the same license as the original package.
>   * A manifest file listing the configured packages and related information.
>   * The license text of the packages; they have been saved in the licenses/
>     subdirectory.
> -- 
> 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-01 20:21 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
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 [this message]

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=20160201202109.GE4278@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox