From: aep <aep@exys.org>
To: <musl@lists.openwall.com>
Subject: Re: license survey results
Date: Tue, 06 Mar 2012 17:55:48 +0100 [thread overview]
Message-ID: <889243fc30d601eb627f0ae3df7fe568@exys.org> (raw)
In-Reply-To: <20120228015557.GJ184@brightrain.aerifal.cx>
> In summary, it looks like everyone except Luka (and perhaps aep) who
> responded would like to see at least *some* additional level of
> permissiveness to musl's license terms,
For me each of those options is sufficient. Was just showing a
not-mentioned alternative ;)
Glad to see the majority is leaning towards BSD. Says something about
musls users and direction.
prev parent reply other threads:[~2012-03-06 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 1:55 Rich Felker
2012-02-29 16:01 ` Luka Marčetić
2012-03-01 2:31 ` Isaac Dunham
2012-03-01 2:39 ` Rich Felker
2012-03-06 16:55 ` aep [this message]
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=889243fc30d601eb627f0ae3df7fe568@exys.org \
--to=aep@exys.org \
--cc=musl@lists.openwall.com \
/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.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).