From: atweiden <atweiden@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] nilfs-utils: update to 2.2.9.
Date: Mon, 08 Aug 2022 02:03:58 +0200 [thread overview]
Message-ID: <20220808000358.mSLLBaQ2iWLL-nrKBEFG76x1oyPCEOUlPSgRxDVwfjE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38517@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
New review comment by atweiden on void-packages repository
https://github.com/void-linux/void-packages/pull/38517#discussion_r939741587
Comment:
Ah, OK. Grepping `COPYING` from source:
```
GNU GENERAL PUBLIC LICENSE
[…]
9. The Free Software Foundation may publish revised and/or new versions
of the General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any
later version", you have the option of following the terms and conditions
either of that version or of any later version published by the Free
Software Foundation. If the Program does not specify a version number of
this License, you may choose any version ever published by the Free Software
Foundation.
```
But this may not be the author’s intention, e.g. the source code states `Licensed under GPLv2`, `Licensed under LGPLv2` in many places.
I’ll change the license.
next prev parent reply other threads:[~2022-08-08 0:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 11:48 [PR PATCH] " atweiden
2022-08-07 15:04 ` [PR REVIEW] " sgn
2022-08-07 15:04 ` sgn
2022-08-07 15:04 ` sgn
2022-08-07 15:04 ` sgn
2022-08-07 15:04 ` sgn
2022-08-08 0:03 ` atweiden [this message]
2022-08-08 0:10 ` [PR PATCH] [Updated] " atweiden
2022-08-08 0:23 ` [PR REVIEW] " sgn
2022-08-08 0:23 ` sgn
2022-08-08 0:25 ` sgn
2022-08-08 5:53 ` [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=20220808000358.mSLLBaQ2iWLL-nrKBEFG76x1oyPCEOUlPSgRxDVwfjE@z \
--to=atweiden@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).