Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rahul Bedarkar <rahulbedarkar89@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/manual: contribute: fix license string for Buildroot license
Date: Sat, 15 Apr 2017 10:44:40 +0530	[thread overview]
Message-ID: <1492233280-5237-1-git-send-email-rahulbedarkar89@gmail.com> (raw)

As per section 12.2 "Complying with the Buildroot license", Buildroot
is released under GPL version 2 or (at your option) any later version.
But SPDX license string for Buildroot license in section 21.5
"Submitting patches" refers to only GPL version 2. Fix this
inconsistency by using correct SPDX identifier.

Signed-off-by: Rahul Bedarkar <rahulbedarkar89@gmail.com>
---
 docs/manual/contribute.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/manual/contribute.txt b/docs/manual/contribute.txt
index 4ec01a8..719032b 100644
--- a/docs/manual/contribute.txt
+++ b/docs/manual/contribute.txt
@@ -227,7 +227,7 @@ Finally, the patch should be signed off. This is done by adding
 +Signed-off-by: Your Real Name <your@email.address>+ at the end of the
 commit message. +git commit -s+ does that for you, if configured
 properly. The +Signed-off-by+ tag means that you publish the patch
-under the Buildroot license (i.e. GPL-2.0, except for package patches,
+under the Buildroot license (i.e. GPL-2.0+, except for package patches,
 which have the upstream license), and that you are allowed to do so.
 See http://developercertificate.org/[the Developer Certificate of
 Origin] for details.
-- 
2.7.4

             reply	other threads:[~2017-04-15  5:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-15  5:14 Rahul Bedarkar [this message]
2017-04-15  8:24 ` [Buildroot] [PATCH] docs/manual: contribute: fix license string for Buildroot license Thomas Petazzoni

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=1492233280-5237-1-git-send-email-rahulbedarkar89@gmail.com \
    --to=rahulbedarkar89@gmail.com \
    --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