From: David Craven <david@craven.ch>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 1/2] gnu: Add libtsm.
Date: Tue, 23 Aug 2016 00:25:22 +0200 [thread overview]
Message-ID: <CAL1_im=G+-wntCOSz-X=btvpJFws-tgL2SOcwvpuUYK7=Hk_8w@mail.gmail.com> (raw)
In-Reply-To: <CAL1_immH0Zw=x-un8kbxZ-xTzG_B880_HfPipCtbh4uvLOrp5w@mail.gmail.com>
>>> The new license bars us from redistributing the code for a fee? If so,
>>> does that count as free software?
>>
>>> But regardless of how you got your copies, you always have the freedom
>>> to copy and change the software, even to sell copies.
>>
>> I guess not then. It has to be removed then?
>
> I could also ask the author of those two files (wcwidth.h, wcwidth.c)
> if he can make them available under the full ISC license...
The FSDG defiler has struck again =P I think this can wait until tomorrow...
next prev parent reply other threads:[~2016-08-22 22:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 13:53 [PATCH 1/2] gnu: Add libtsm David Craven
2016-08-22 13:53 ` [PATCH 2/2] gnu: Add kmscon David Craven
2016-08-22 18:10 ` Danny Milosavljevic
2016-08-22 18:14 ` David Craven
2016-08-22 18:17 ` David Craven
2016-08-22 19:34 ` Leo Famulari
2016-08-24 18:16 ` Efraim Flashner
2016-08-24 18:56 ` David Craven
2016-08-22 19:33 ` [PATCH 1/2] gnu: Add libtsm Leo Famulari
2016-08-22 20:54 ` David Craven
2016-08-22 20:57 ` David Craven
2016-08-22 21:08 ` Leo Famulari
2016-08-22 21:46 ` David Craven
2016-08-22 21:52 ` Leo Famulari
2016-08-22 21:58 ` David Craven
2016-08-22 22:10 ` David Craven
2016-08-22 22:25 ` David Craven [this message]
2016-08-23 0:04 ` David Craven
2016-08-23 1:09 ` Leo Famulari
2016-08-24 18:22 ` Efraim Flashner
2016-08-24 18:54 ` David Craven
2016-08-24 18:57 ` Leo Famulari
2016-08-24 19:11 ` David Craven
2016-08-28 13:14 ` David Craven
2016-08-28 15:11 ` Ludovic Courtès
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='CAL1_im=G+-wntCOSz-X=btvpJFws-tgL2SOcwvpuUYK7=Hk_8w@mail.gmail.com' \
--to=david@craven.ch \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).