From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] New package: senpai-0.0.20211223
Date: Sat, 09 Apr 2022 13:29:56 +0200 [thread overview]
Message-ID: <20220409112956.oWRAua57XFHPo7uI7qbdgFRuAEcyE7G0ODvsxWlwrzs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34721@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 520 bytes --]
New review comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/34721#discussion_r846620442
Comment:
Yes, but it's against [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements). If software has releases, we can be sure they tested it and consider it to be stable at that point. If not, we have to do all the testing, patching and deciding at what point it's stable on our own which is a big effort for some packages.
next prev parent reply other threads:[~2022-04-09 11:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 16:41 [PR PATCH] " kedodrill
2021-12-27 16:47 ` [PR PATCH] [Updated] " kedodrill
2022-04-09 9:35 ` [PR REVIEW] " paper42
2022-04-09 9:35 ` paper42
2022-04-09 9:35 ` paper42
2022-04-09 11:20 ` eoli3n
2022-04-09 11:29 ` paper42 [this message]
2022-04-09 16:03 ` kedodrill
2022-04-09 16:03 ` kedodrill
2022-04-09 16:17 ` kedodrill
2022-06-17 19:28 ` [PR PATCH] [Updated] " kedodrill
2022-06-17 19:30 ` kedodrill
2022-06-17 19:34 ` kedodrill
2022-06-17 19:35 ` [PR REVIEW] " kedodrill
2022-08-01 13:05 ` [PR REVIEW] New package: senpai-0.0.20220611 kedodrill
2022-08-10 22:35 ` [PR PATCH] [Updated] " kedodrill
2022-08-10 22:41 ` [PR PATCH] [Updated] New package: senpai-0.1.0 kedodrill
2022-08-10 22:41 ` [PR REVIEW] " kedodrill
2022-08-10 22:44 ` [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=20220409112956.oWRAua57XFHPo7uI7qbdgFRuAEcyE7G0ODvsxWlwrzs@z \
--to=paper42@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).