From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: parsec: update to 150
Date: Wed, 08 Jan 2020 22:34:07 +0100 [thread overview]
Message-ID: <20200108213407.GIArAywYLk3IdZGa4KbtjVAr1TcX2cySxYNjJDuJHmg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18077@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
New comment by silvernode on void-packages repository
https://github.com/void-linux/void-packages/pull/18077#issuecomment-572267134
Comment:
Parsec does not ship a license file with their debian package and only have a terms of service page with a license section which is one paragraph. Should I just not include the license variable at all? the Manual says if there is no license file to default to BSD-2-clause, but xlint complains that there is still no license file. Not sure what to do next. This template was previously merged with license var the way it is.
next prev parent reply other threads:[~2020-01-08 21:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 17:34 [PR PATCH] " voidlinux-github
2020-01-08 17:29 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-08 17:33 ` voidlinux-github
2020-01-08 18:23 ` voidlinux-github
2020-01-08 21:34 ` voidlinux-github [this message]
2020-01-09 21:44 ` voidlinux-github
2020-01-12 3:27 ` voidlinux-github
2020-01-12 3:27 ` voidlinux-github
2020-01-12 6:51 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-12 9:56 ` voidlinux-github
2020-01-12 10:07 ` [PR PATCH] [Updated] parsec: update to 150 [ci-skip] voidlinux-github
2020-01-12 10:09 ` voidlinux-github
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=20200108213407.GIArAywYLk3IdZGa4KbtjVAr1TcX2cySxYNjJDuJHmg@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).