From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/manual: add info about AGPLv3 license
Date: Sun, 21 Feb 2016 00:11:30 +0100 [thread overview]
Message-ID: <56C8F2A2.1040603@mind.be> (raw)
In-Reply-To: <1456002529-21636-1-git-send-email-yegorslists@googlemail.com>
On 02/20/16 22:08, Yegor Yefremov wrote:
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Since we have this for mongodb and monit, this could probably be considered a
bugfix so for 2016.02.
Regards,
Arnout
> ---
> docs/manual/legal-notice.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/docs/manual/legal-notice.txt b/docs/manual/legal-notice.txt
> index 5895224..0a91c37 100644
> --- a/docs/manual/legal-notice.txt
> +++ b/docs/manual/legal-notice.txt
> @@ -74,6 +74,9 @@ file to inform you of relevant material that could not be saved.
> Here is a list of the licenses that are most widely used by packages in
> Buildroot, with the name used in the manifest files:
>
> +* `AGPLv3`:
> + http://www.gnu.org/licenses/agpl-3.0.en.html[
> + GNU Affero General Public License, version 3];
> * `GPLv2`:
> http://www.gnu.org/licenses/old-licenses/gpl-2.0.html[
> GNU General Public License, version 2];
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2016-02-20 23:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 21:08 [Buildroot] [PATCH] docs/manual: add info about AGPLv3 license Yegor Yefremov
2016-02-20 23:11 ` Arnout Vandecappelle [this message]
2016-02-21 8:40 ` Peter Korsgaard
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=56C8F2A2.1040603@mind.be \
--to=arnout@mind.be \
--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