From: Oliver Schneider <musl-mailinglist@f-prot.com>
To: musl@lists.openwall.com
Subject: Re: How to properly give attribution to musl-libc?
Date: Fri, 07 Feb 2014 13:33:45 +0000 [thread overview]
Message-ID: <52F4E0B9.1020107@f-prot.com> (raw)
In-Reply-To: <20140207010342.GK15627@brightrain.aerifal.cx>
Hi Rich,
On 2014-02-07 01:03, Rich Felker wrote:
> For the technical sake of conformance to the conditions in the
> relevant licenses, I believe it's sufficient to include somewhere with
> the distributed binary (not necessarily in the binary itself; an
> accompanying text file is perfectly reasonable) a statement with the
> copyright and permission notice.
Okay, thanks.
> Of course if you find musl useful and would like to help promote it,
> other things like putting a notice and link on the website, etc. would
> be great. (As an aside, perhaps we should prepare some "powered by
> musl" etc. "button" graphics that websites can display.)
I find it useful as individual and professional, but of course the
decisions to promote it are only up to me as an individual. For anything
else I must ask.
> No, this is actually an FAQ topic. :-)
>
> http://wiki.musl-libc.org/wiki/FAQ#Q:_why_is_there_no_MUSL_macro_.3F
I know about this one. I read this somewhere on some mailing list
before, when I was searching for Clang support and found that there was
some mentioning of this fact in the glibc or GCC community, don't
remember exactly. Either way, I was first astonished, but after a second
thought it made perfect sense. Conform to the standards and you needn't
provide crutches.
I guess I'll simply define something on the command line for musl-libc
builds. Currently they are only an option, but eventually they're meant
to replace the glibc ones.
Thanks,
// Oliver
prev parent reply other threads:[~2014-02-07 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 19:06 Oliver Schneider
2014-02-07 1:03 ` Rich Felker
2014-02-07 13:33 ` Oliver Schneider [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=52F4E0B9.1020107@f-prot.com \
--to=musl-mailinglist@f-prot.com \
--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).