From: ailiop-git <ailiop-git@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pounce: update to 2.5.
Date: Sat, 25 Sep 2021 13:41:29 +0200 [thread overview]
Message-ID: <20210925114129.cSAB70ZXwMoylWXIt43AwfQG4hCGyBvyqtmPMuo7hhY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33110@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
New comment by ailiop-git on void-packages repository
https://github.com/void-linux/void-packages/pull/33110#issuecomment-927108964
Comment:
> From our point of view, all commits look like untested low effort version bumps that might or might not be tested on a whole lot of 1 system.
That sounds about right. I do not see how submitters ticking on any of those boxes helps in changing this assumption. Whether I use it regularly or I "lightly tested it", should not influence a reviewer's decision, and it is anyway a completely vague statement with no content.
The "this is a new package" checkbox is also rather useless, given that this is obvious from the diff.
> E.g. #32707 did break on x86_64-musl, you did never tried to fix it or ask someone to help with it.
> Such PR's just make it look like you do not care about these updates.
Sorry, but I simply do not have the bandwidth to deal with all test failures and all archs. That also goes on to show how irrelevant those checkboxes are, especially given that travis will anyway build all targets. What difference would it make to any reviewer if I stated that I've built this on x86_64? It's obvious from the travis results what works and what not.
next prev parent reply other threads:[~2021-09-25 11:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 10:23 [PR PATCH] " ailiop-git
2021-09-25 10:58 ` paper42
2021-09-25 11:00 ` ailiop-git
2021-09-25 11:06 ` paper42
2021-09-25 11:09 ` ailiop-git
2021-09-25 11:25 ` paper42
2021-09-25 11:27 ` Johnnynator
2021-09-25 11:41 ` ailiop-git [this message]
2021-09-25 11:58 ` ahesford
2021-09-25 12:03 ` paper42
2021-09-25 12:14 ` ailiop-git
2021-09-25 13:04 ` ahesford
2021-09-27 11:39 ` [PR PATCH] [Merged]: " paper42
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=20210925114129.cSAB70ZXwMoylWXIt43AwfQG4hCGyBvyqtmPMuo7hhY@z \
--to=ailiop-git@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).