From: jason1987d <jason1987d@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: finviz-1.44
Date: Wed, 20 Jul 2022 05:28:06 +0200 [thread overview]
Message-ID: <20220720032806.m4RGuN_neifro-i4eYexnIVcJxxKr-xrA-7bgg5EiHI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38146@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 465 bytes --]
New comment by jason1987d on void-packages repository
https://github.com/void-linux/void-packages/pull/38146#issuecomment-1189772655
Comment:
> it's not our job as downstream to fix their changelog. if it doesn't look like upstream is updating it, imo just leave it out as it's not very informative to users.
What would I remove then to make the tests pass? Remove just the changelog.md file itself?
Also noting the tests fail even when I use pypi instead.
next prev parent reply other threads:[~2022-07-20 3:28 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 23:34 [PR PATCH] " jason1987d
2022-07-19 23:45 ` [PR PATCH] [Updated] " jason1987d
2022-07-19 23:46 ` jason1987d
2022-07-19 23:54 ` [PR REVIEW] " classabbyamp
2022-07-19 23:54 ` classabbyamp
2022-07-19 23:54 ` classabbyamp
2022-07-19 23:54 ` classabbyamp
2022-07-20 0:00 ` jason1987d
2022-07-20 0:02 ` [PR PATCH] [Updated] " jason1987d
2022-07-20 0:03 ` jason1987d
2022-07-20 0:05 ` jason1987d
2022-07-20 0:13 ` [PR REVIEW] " classabbyamp
2022-07-20 0:54 ` [PR PATCH] [Updated] " jason1987d
2022-07-20 0:55 ` [PR REVIEW] " jason1987d
2022-07-20 1:05 ` classabbyamp
2022-07-20 1:26 ` jason1987d
2022-07-20 1:27 ` jason1987d
2022-07-20 1:37 ` [PR PATCH] [Updated] " jason1987d
2022-07-20 1:42 ` [PR REVIEW] " jason1987d
2022-07-20 1:42 ` jason1987d
2022-07-20 1:42 ` jason1987d
2022-07-20 1:44 ` [PR PATCH] [Updated] " jason1987d
2022-07-20 1:49 ` jason1987d
2022-07-20 1:59 ` [PR REVIEW] " jason1987d
2022-07-20 2:19 ` jason1987d
2022-07-20 2:44 ` jason1987d
2022-07-20 3:00 ` classabbyamp
2022-07-20 3:17 ` jason1987d
2022-07-20 3:21 ` [PR PATCH] [Updated] " jason1987d
2022-07-20 3:27 ` jason1987d
2022-07-20 3:28 ` classabbyamp
2022-07-20 3:28 ` jason1987d [this message]
2022-07-20 3:29 ` jason1987d
2022-07-20 3:33 ` jason1987d
2022-07-20 4:18 ` classabbyamp
2022-07-20 5:10 ` [PR PATCH] [Updated] " jason1987d
2022-07-20 5:16 ` jason1987d
2022-07-20 13:15 ` jason1987d
2022-07-20 20:41 ` [PR PATCH] [Updated] " jason1987d
2022-07-20 21:03 ` jason1987d
2022-07-20 21:10 ` jason1987d
2022-07-20 21:14 ` jason1987d
2022-07-20 22:03 ` jason1987d
2022-07-20 22:14 ` jason1987d
2022-07-20 22:34 ` jason1987d
2022-07-20 23:02 ` jason1987d
2022-07-21 13:24 ` jason1987d
2022-07-22 0:09 ` [PR PATCH] [Updated] " jason1987d
2022-07-22 0:31 ` jason1987d
2022-07-22 0:32 ` [PR PATCH] [Closed]: " jason1987d
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=20220720032806.m4RGuN_neifro-i4eYexnIVcJxxKr-xrA-7bgg5EiHI@z \
--to=jason1987d@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).