From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 4/4] examples/public-inbox.psgi: relax license to GPL-3.0+
Date: Mon, 29 Feb 2016 00:02:19 +0000 [thread overview]
Message-ID: <20160229000219.18575-5-e@80x24.org> (raw)
In-Reply-To: <20160229000219.18575-1-e@80x24.org>
Using the AGPL for server config files is probably overkill.
GPL-3.0+ still requires appliance vendors to disclose
configurations which seems desirable for end users.
---
examples/public-inbox.psgi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/examples/public-inbox.psgi b/examples/public-inbox.psgi
index f574912..dcca3b0 100644
--- a/examples/public-inbox.psgi
+++ b/examples/public-inbox.psgi
@@ -1,6 +1,6 @@
#!/usr/bin/perl -w
-# Copyright (C) 2014-2015 all contributors <meta@public-inbox.org>
-# License: AGPLv3 or later (https://www.gnu.org/licenses/agpl-3.0.txt)
+# Copyright (C) 2014-2016 all contributors <meta@public-inbox.org>
+# License: GPL-3.0+ <https://www.gnu.org/licenses/gpl-3.0.txt>
# Note: this is part of our test suite, update t/plack.t if this changes
# Usage: plackup [OPTIONS] /path/to/this/file
# A startup command for development which monitors changes:
--
EW
next prev parent reply other threads:[~2016-02-29 0:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 0:02 [PATCH 0/4] various example updates Eric Wong
2016-02-29 0:02 ` [PATCH 1/4] examples/: PSGI " Eric Wong
2016-02-29 0:02 ` [PATCH 2/4] examples/cgi-webrick.rb: set CGIPathEnv, update comments Eric Wong
2016-02-29 0:02 ` [PATCH 3/4] examples: various Apache-related doc updates Eric Wong
2016-02-29 0:02 ` Eric Wong [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-29 1:45 [PATCH 2/4] examples/cgi-webrick.rb: set CGIPathEnv, update comments Eric Wong
2016-02-29 1:45 ` [PATCH 4/4] examples/public-inbox.psgi: relax license to GPL-3.0+ Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160229000219.18575-5-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).