From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Mon, 1 Feb 2016 19:53:12 +0100 Subject: [Buildroot] [PATCH 2/5] docs/manual: slightly clarify patch licensing In-Reply-To: <1454338344-24973-3-git-send-email-luca@lucaceresoli.net> References: <1454338344-24973-1-git-send-email-luca@lucaceresoli.net> <1454338344-24973-3-git-send-email-luca@lucaceresoli.net> Message-ID: <20160201195312.09e2d34f@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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 > --- > 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" ? Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com