From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5] docs/manual: add section about patch licensing
Date: Mon, 1 Feb 2016 23:12:49 +0100 [thread overview]
Message-ID: <56AFD861.9060006@lucaceresoli.net> (raw)
In-Reply-To: <20160201195534.2501419b@free-electrons.com>
Hi Thomas,
Thomas Petazzoni wrote:
> Dear Luca Ceresoli,
>
> On Mon, 1 Feb 2016 15:52:23 +0100, Luca Ceresoli wrote:
>> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
>> ---
>> docs/manual/legal-notice.txt | 16 ++++++++++++++--
>> docs/manual/patch-policy.txt | 2 +-
>> 2 files changed, 15 insertions(+), 3 deletions(-)
>
>> Patches are released under the same license as the software that they
>> -modify.
>> +modify (see xref:legal-info-buildroot[]).
>
> apply to ?
Of course, queued for v2.
--
Luca
next prev parent reply other threads:[~2016-02-01 22:12 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 [this message]
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=56AFD861.9060006@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 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.