From: heliocat <heliocat@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] iat: fix license, description
Date: Sun, 04 Jul 2021 20:16:52 +0200 [thread overview]
Message-ID: <20210704181652.dgNePBrlZ4kr-OXtAWyazqiU-U6j8fD3e5m9cP6o92U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31753@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 276 bytes --]
New review comment by heliocat on void-packages repository
https://github.com/void-linux/void-packages/pull/31753#discussion_r663539162
Comment:
I looked a second time, that's the BSD-2-Clause license text, just with a "this is licensed under the GPL" header slapped on it.
next prev parent reply other threads:[~2021-07-04 18:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 19:00 [PR PATCH] " heliocat
2021-07-03 0:07 ` [PR REVIEW] " sgn
2021-07-04 18:10 ` heliocat
2021-07-04 18:16 ` heliocat [this message]
2021-07-04 18:22 ` [PR PATCH] [Updated] " heliocat
2021-07-24 2:25 ` [PR PATCH] [Merged]: " sgn
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=20210704181652.dgNePBrlZ4kr-OXtAWyazqiU-U6j8fD3e5m9cP6o92U@z \
--to=heliocat@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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).