| Message ID | 1454365196-26319-3-git-send-email-luca@lucaceresoli.net |
|---|---|
| State | Accepted |
| Commit | 8ab41aed2c30ae7d040551224f579c2d8b3adc3e |
| Headers | show |
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 >
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 >
On 01-02-16 23:19, 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 <luca@lucaceresoli.net> > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Please still add this in 2016.02. Regards, Arnout > > --- > 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. >
>>>>> "Luca" == Luca Ceresoli <luca@lucaceresoli.net> writes: > 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> > --- > Changes v1 -> v2: > - "they modify" -> "they apply to" (Thomas). Committed, thanks.
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.
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> --- Changes v1 -> v2: - "they modify" -> "they apply to" (Thomas). --- docs/manual/patch-policy.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)