From: Adam Van Ymeren <adam@vany.ca>
To: Tobias Geerinckx-Rice <me@tobias.gr>, 28973@debbugs.gnu.org
Subject: [bug#28973] [PATCH 1/1] gnu: Add strongswan.
Date: Mon, 15 Jan 2018 17:32:45 -0500 [thread overview]
Message-ID: <9A48E196-BC5C-425B-8EB0-D944D464BD3D@vany.ca> (raw)
In-Reply-To: <9b85d987-e691-a89e-f4ee-1ce663b5c928@tobias.gr>
On January 15, 2018 4:50:08 PM EST, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
>There's always the non-copyleft procedure for uncommon (but free)
>licences that don't have their own entry.
Didn't know about that. That's probably the right thing to use here?
>
>Is that the entire licence text? It sounds strange to me (exception to
>what?). I'm obviously not clever enough to be a lawyer.
Yeah thats the entire licence text, it is strange. It's similar to what appears in the top of '"configure" scripts as generated by autoconf.
>
>Yay,
>
>T G-R
next prev parent reply other threads:[~2018-01-15 22:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 18:58 [bug#28973] [PATCH 1/1] gnu: Add strongswan Adam Van Ymeren
2017-10-24 20:05 ` [bug#28973] [PATCH] Add the patches necessary to build strongswan Adam Van Ymeren
2017-10-24 20:11 ` [bug#28973] [PATCH 1/1] gnu: Add strongswan Tobias Geerinckx-Rice
2017-10-24 23:08 ` Adam Van Ymeren
2017-11-19 22:43 ` Ludovic Courtès
2017-11-19 23:20 ` Adam Van Ymeren
2018-01-11 21:48 ` Ludovic Courtès
2018-01-12 17:15 ` Adam Van Ymeren
2018-01-13 13:52 ` Ludovic Courtès
2018-01-13 14:00 ` Tobias Geerinckx-Rice
2018-01-15 20:36 ` Adam Van Ymeren
2018-01-15 21:50 ` Tobias Geerinckx-Rice
2018-01-15 22:32 ` Adam Van Ymeren [this message]
2018-01-30 21:22 ` Ludovic Courtès
2018-01-31 19:46 ` Adam Van Ymeren
2018-01-31 22:33 ` bug#28973: " Ludovic Courtès
2017-10-24 20:13 ` [bug#28973] " Tobias Geerinckx-Rice
2018-01-23 20:43 ` [bug#28973] Updated: " Adam Van Ymeren
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9A48E196-BC5C-425B-8EB0-D944D464BD3D@vany.ca \
--to=adam@vany.ca \
--cc=28973@debbugs.gnu.org \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).