From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] monit: add license information
Date: Mon, 15 Apr 2013 23:54:45 +0200 [thread overview]
Message-ID: <87eheblas9.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1366011607-31433-1-git-send-email-spdawson@gmail.com> (spdawson@gmail.com's message of "Mon, 15 Apr 2013 08:40:07 +0100")
>>>>> "spdawson" == spdawson <spdawson@gmail.com> writes:
spdawson> From: Simon Dawson <spdawson@gmail.com>
spdawson> Signed-off-by: Simon Dawson <spdawson@gmail.com>
spdawson> ---
spdawson> package/monit/monit.mk | 2 ++
spdawson> 1 file changed, 2 insertions(+)
spdawson> diff --git a/package/monit/monit.mk b/package/monit/monit.mk
spdawson> index a8b6447..0d24e05 100644
spdawson> --- a/package/monit/monit.mk
spdawson> +++ b/package/monit/monit.mk
spdawson> @@ -6,6 +6,8 @@
spdawson> MONIT_VERSION = 5.4
spdawson> MONIT_SITE = http://mmonit.com/monit/dist/
spdawson> +MONIT_LICENSE = AGPLv3+
Hmm, I see very few files mentioning the 'any later version':
grep -rls 'any later version' *
aclocal.m4
config/config.sub
config/ltmain.sh
config/missing
config/config.guess
configure
COPYING
libmonit/config/config.sub
libmonit/config/ltmain.sh
libmonit/config/missing
libmonit/config/config.guess
libmonit/m4/libtool.m4
libmonit/configure
libmonit/aclocal.m4
libmonit/COPYING
libmonit/libtool
src/tokens.h
src/protocols/sip.c
src/protocols/lmtp.c
src/y.tab.c
E.G. basically no source files.
src/monit.c also talks about a special openssl exception.
How should we handle this?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-04-15 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 7:40 [Buildroot] [PATCH] monit: add license information spdawson at gmail.com
2013-04-15 21:54 ` Peter Korsgaard [this message]
2013-04-16 13:48 ` Simon Dawson
2013-04-17 16:04 ` Arnout Vandecappelle
2013-04-18 9:24 ` Simon Dawson
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=87eheblas9.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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