From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] WIP: python3-ansible-lint: update to 6.0.0a1.
Date: Mon, 14 Mar 2022 08:49:30 +0100 [thread overview]
Message-ID: <20220314074930.uS4lU0lQTYTSyoR8McMCAYdq6YRps1A6aA2kjyH6uSQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36131@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
New review comment by jcgruenhage on void-packages repository
https://github.com/void-linux/void-packages/pull/36131#discussion_r825664979
Comment:
> The ansible-lint project is distributed as [GPLv3](https://github.com/ansible-community/ansible-lint/blob/main/COPYING) due to use of [GPLv3](https://github.com/ansible-community/ansible-lint/blob/main/COPYING) runtime dependencies, like ansible and yamllint.
>
> For historical reasons, its own code-base remains licensed under a more liberal [MIT](https://github.com/ansible-community/ansible-lint/blob/main/docs/licenses/LICENSE.mit.txt) license and any contributions made are accepted as being made under original [MIT](https://github.com/ansible-community/ansible-lint/blob/main/docs/licenses/LICENSE.mit.txt) license.
next prev parent reply other threads:[~2022-03-14 7:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 7:44 [PR PATCH] " jcgruenhage
2022-03-14 7:49 ` jcgruenhage [this message]
2022-03-14 7:50 ` [PR REVIEW] " jcgruenhage
2022-03-14 8:15 ` ssbarnea
2022-03-15 10:37 ` [PR PATCH] [Updated] " jcgruenhage
2022-03-24 16:16 ` [PR PATCH] [Updated] python3-ansible-lint: update to 6.0.0 jcgruenhage
2022-03-24 22:24 ` [PR REVIEW] python3-ansible-lint: update to 6.0.2 paper42
2022-03-24 22:25 ` paper42
2022-03-25 9:33 ` [PR PATCH] [Updated] " jcgruenhage
2022-03-25 9:38 ` [PR REVIEW] " jcgruenhage
2022-03-25 9:39 ` jcgruenhage
2022-04-07 16:54 ` [PR PATCH] [Merged]: " leahneukirchen
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=20220314074930.uS4lU0lQTYTSyoR8McMCAYdq6YRps1A6aA2kjyH6uSQ@z \
--to=jcgruenhage@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).