[Buildroot] [git commit] docs/manual: slightly clarify patch licensing

Peter Korsgaard peter at korsgaard.com
Thu Feb 25 10:33:00 UTC 2016

commit: https://git.buildroot.net/buildroot/commit/?id=8ab41aed2c30ae7d040551224f579c2d8b3adc3e
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master

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 at lucaceresoli.net>
Cc: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
Acked-by: "Yann E. MORIN" <yann.morin.1998 at free.fr>
Acked-by: "Yann E. MORIN" <yann.morin.1998 at free.fr>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout at mind.be>
Signed-off-by: Peter Korsgaard <peter at korsgaard.com>
 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
+Patches are released under the same license as the software they apply
 A message explaining what the patch does, and why it is needed, should
 be added in the header commentary of the patch.

More information about the buildroot mailing list