From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Copyright/license of libc-testsuite
Date: Thu, 4 Feb 2016 20:27:29 +0100 [thread overview]
Message-ID: <20160204192728.GD9915@port70.net> (raw)
In-Reply-To: <56B39F98.8060605@codeplay.com>
* Jeroen Ketema <jeroen@codeplay.com> [2016-02-04 18:59:36 +0000]:
> Browsing the gitc web interface on the musl website, I encountered
> libc-testsuite, which seems to cover part of my needs. However, the suite
> does not seem to have a license and/or copyright associated with it, which
> makes it somewhat difficult to evaluate whether I can actually use the
> testsuite in the context I'm working in. Would it be possible to get some
> clarification with respect to the testsuite's copyright and license?
you mean http://repo.or.cz/libc-test.git ?
it has
http://repo.or.cz/libc-test.git/blob/HEAD:/COPYRIGHT
with a separate AUTHORS file.
however my policy is to add arbitraryly licensed
tests (with the license text included somewhere).
(this way we cannot distribute the tests with musl,
but we can have all openly available sources for
tests, i don't know any license that prevents you
from running tests against code under that license.)
> This email and any attachments may contain confidential and /or privileged
> information and is for use by the addressee only. If you are not the intended
> recipient, please notify Codeplay Software Ltd immediately and delete the
> message from your computer. You may not copy or forward it,or use or disclose
> its contents to any other person. Any views or other information in this message
this is bad for public mailing lists.
> which do not relate to our business are not authorized by Codeplay software Ltd,
> nor does this message form part of any contract unless so stated.
>
> As internet communications are capable of data corruption Codeplay Software Ltd
> does not accept any responsibility for any changes made to this message after it
> was sent. Please note that Codeplay Software Ltd does not accept any liability
> or responsibility for viruses and it is your responsibility to scan any
> attachments.
>
> Company registered in England and Wales, number: 04567874
> Registered office: 81 Linkfield Street, Redhill RH1 6BY
prev parent reply other threads:[~2016-02-04 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 18:59 Jeroen Ketema
2016-02-04 19:24 ` Rich Felker
2016-02-04 19:34 ` Jeroen Ketema
2016-02-04 19:27 ` Szabolcs Nagy [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=20160204192728.GD9915@port70.net \
--to=nsz@port70.net \
--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).