From: "Ludovic Courtès" <ludo@gnu.org>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: 34613@debbugs.gnu.org, Pierre Neidhardt <mail@ambrevar.xyz>
Subject: [bug#34613] Acknowledgement ([PATCH] gnu: Add prometheus.)
Date: Mon, 18 Mar 2019 09:31:10 +0100 [thread overview]
Message-ID: <87pnqotwhd.fsf@gnu.org> (raw)
In-Reply-To: <CAE4v=piqORpLwLiZ_QZHeF+DidnA_-E_C+6CMZU4jZ4L2xt7Ow@mail.gmail.com> ("Gábor Boskovits"'s message of "Wed, 13 Mar 2019 13:33:24 +0100")
Hi,
Gábor Boskovits <boskovits@gmail.com> skribis:
> 2019. márc. 13., Sze 11:06 dátummal Ludovic Courtès <ludo@gnu.org> ezt írta:
[...]
>> The thing is, Glyphicons does seem to be non-free, so if it ends up
>> being included one way or another, we have a problem. I would have
>> expected Debian to provide replacement icons or something like that.
>>
> In the case it is included, as part of bootstrap, it is under the apache
> license, because of a special agreement, that when it is part of bootstrap
> it is dual licensed to this effect. My current evaluation is that it is ok
> to include the package as is.
OK, sounds good.
Thank you for explaining!
Ludo’.
next prev parent reply other threads:[~2019-03-18 8:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 11:45 [bug#34613] [PATCH] gnu: Add prometheus Gábor Boskovits
[not found] ` <handler.34613.B.155083599830524.ack@debbugs.gnu.org>
2019-02-22 12:21 ` [bug#34613] Acknowledgement ([PATCH] gnu: Add prometheus.) Gábor Boskovits
2019-03-11 22:19 ` Ludovic Courtès
2019-03-12 7:03 ` Pierre Neidhardt
2019-03-12 19:31 ` Leo Famulari
2019-03-12 21:24 ` Gábor Boskovits
2019-03-12 21:29 ` Gábor Boskovits
2019-03-13 10:06 ` Ludovic Courtès
2019-03-13 12:33 ` Gábor Boskovits
2019-03-18 8:31 ` Ludovic Courtès [this message]
2022-04-07 12:29 ` [bug#34613] [PATCH] gnu: Add prometheus zimoun
2022-10-08 14:42 ` zimoun
2022-10-18 16:18 ` bug#34613: " zimoun
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=87pnqotwhd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=34613@debbugs.gnu.org \
--cc=boskovits@gmail.com \
--cc=mail@ambrevar.xyz \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.