From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: New packages: intellij-idea-ultimate-edition-2019.1.3, CLion-2019.1.4, WebStorm-2019.1.3, GoLand-2019.1.3, RubyMine-2019.1.2
Date: Sat, 22 Jun 2019 20:09:04 +0200 [thread overview]
Message-ID: <20190622180904.Ojad6ax131CKRdhd210-4HWqHw4q6HivQRRl_NWIfXs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11736@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 589 bytes --]
New comment by 2asoft on void-packages repository
https://github.com/void-linux/void-packages/pull/11736#issuecomment-504686974
Comment:
> Don't get xlint that strict. That rule was created to make people aware that license should be included, but if vcopy is used to include them it's okay to ignore error as false positive. Better to have simple template. Or one can silence error with comment containing word `vlicense`.
Ok, done.
> If one build is tested, all travis build passes and template is not too hackish, it is fine to ship.
That's fair.
Added the i686 builds back.
next prev parent reply other threads:[~2019-06-22 18:09 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11736@inbox.vuxu.org>
2019-06-10 1:06 ` [PR PATCH] [Updated] New packages: intellij-idea-ultimate-edition-2019.1.1, CLion-2019.1.2, WebStorm-2019.1.1, GoLand-2019.1.1, RubyMine-2019.1.1 voidlinux-github
2019-06-11 20:47 ` voidlinux-github
2019-06-15 17:53 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-15 17:53 ` voidlinux-github
2019-06-15 17:56 ` voidlinux-github
2019-06-15 17:58 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-15 17:58 ` voidlinux-github
2019-06-15 22:25 ` New packages: intellij-idea-ultimate-edition-2019.1.3, CLion-2019.1.4, WebStorm-2019.1.3, GoLand-2019.1.3, RubyMine-2019.1.2 voidlinux-github
2019-06-18 6:09 ` voidlinux-github
2019-06-18 15:26 ` voidlinux-github
2019-06-20 7:06 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-20 7:06 ` voidlinux-github
2019-06-20 7:08 ` voidlinux-github
2019-06-20 7:08 ` voidlinux-github
2019-06-22 18:09 ` voidlinux-github [this message]
2019-06-22 18:17 ` voidlinux-github
2019-06-23 6:09 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-23 6:09 ` voidlinux-github
2019-06-23 6:10 ` voidlinux-github
2019-06-23 6:10 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-23 6:10 ` voidlinux-github
2019-06-23 19:54 ` voidlinux-github
2019-06-23 19:54 ` voidlinux-github
2019-06-24 6:09 ` voidlinux-github
2019-06-24 15:11 ` voidlinux-github
2019-06-26 5:39 ` [PR PATCH] [Updated] " voidlinux-github
2019-06-26 5:39 ` voidlinux-github
2019-06-26 5:39 ` voidlinux-github
2019-06-29 12:09 ` voidlinux-github
2019-06-29 16:45 ` voidlinux-github
2019-06-29 16:45 ` voidlinux-github
2019-07-08 19:53 ` voidlinux-github
2019-07-15 1:33 ` voidlinux-github
2019-10-15 6:31 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-15 6:31 ` voidlinux-github
2019-10-15 16:41 ` voidlinux-github
2019-10-19 20:05 ` voidlinux-github
2019-11-04 19:06 ` voidlinux-github
2019-11-09 6:28 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-22 4:22 ` [PR PATCH] [Updated] New packages: intellij-idea-ultimate-edition-2019.3.1 voidlinux-github
2020-01-22 5:40 ` [PR PATCH] [Merged]: New packages: intellij-idea-ultimate-edition-2019.3.2 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=20190622180904.Ojad6ax131CKRdhd210-4HWqHw4q6HivQRRl_NWIfXs@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).