From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: gama-1.0.7
Date: Tue, 09 Jan 2024 11:41:12 +0100 [thread overview]
Message-ID: <20240109104112.9gSYZFvjbLTOmXOCBJO1XIxbNzNHqUNynVBwkqp7o5U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48123@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
New comment by meator on void-packages repository
https://github.com/void-linux/void-packages/pull/48123#issuecomment-1882828211
Comment:
When there is no [mention of "or later", it is GPL-3.0-only](https://www.gnu.org/licenses/identify-licenses-clearly.html) AFAIK. So the previous notice was valid and it was GPL-3.0-only. But the author changed his license making this clear. These two variants are usually differentiated in license comment headers in code itself, but the project doesn't use these.
But I'm not a license expert.
next prev parent reply other threads:[~2024-01-09 10:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 14:30 [PR PATCH] New package: gama-1.0.4 zen0bit
2024-01-08 22:19 ` [PR PATCH] [Updated] " zen0bit
2024-01-09 0:04 ` zen0bit
2024-01-09 3:57 ` [PR REVIEW] " canack
2024-01-09 4:30 ` [PR PATCH] [Updated] " zen0bit
2024-01-09 8:35 ` zen0bit
2024-01-09 10:41 ` meator [this message]
2024-01-09 11:08 ` New package: gama-1.0.7 canack
2024-01-09 22:46 ` [PR PATCH] [Updated] " zen0bit
2024-01-25 9:35 ` canack
2024-01-25 10:36 ` [PR PATCH] [Updated] " zen0bit
2024-01-25 12:20 ` zen0bit
2024-03-07 17:20 ` [PR PATCH] [Updated] New package: gama-1.1.0 zen0bit
2024-03-12 20:58 ` [PR PATCH] [Updated] New package: gama-1.1.1 zen0bit
2024-03-17 14:30 ` [PR PATCH] [Updated] New package: gama-1.1.2 zen0bit
2024-03-18 10:37 ` zen0bit
2024-03-25 6:33 ` zen0bit
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=20240109104112.9gSYZFvjbLTOmXOCBJO1XIxbNzNHqUNynVBwkqp7o5U@z \
--to=meator@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).