From: chrysos349 <chrysos349@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: incidenceeditor: update to 23.04.2
Date: Thu, 29 Jun 2023 21:14:51 +0200 [thread overview]
Message-ID: <20230629191451.N_1juKuzG6WDLRkXnpF-a3cHhpenH1jqQiBPNTMZtNs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44712@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
New comment by chrysos349 on void-packages repository
https://github.com/void-linux/void-packages/pull/44712#issuecomment-1613667837
Comment:
@ahesford Clearly you're wrong. I tested #44710, #44713, #44714, #44715, #44716 for a bit. I launched[^1] all of them, and used them briefly. I admit i don' know how to properly test #44712, #44711.
All of those are minor releases without any breaking changes in the functionality, etc. What else do i need to do to test them?
There's hardly any information in the manual about how to test different types of packages - apps, libs, python modules, etc. Could you give me any advice?
[^1]: There is this line in CONTRIBUTING.md: "Also, new packages and updates will not be accepted unless they have been runtime tested by installing and running the package."
next prev parent reply other threads:[~2023-06-29 19:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 10:19 [PR PATCH] " chrysos349
2023-06-29 10:29 ` classabbyamp
2023-06-29 10:31 ` chrysos349
2023-06-29 12:28 ` ahesford
2023-06-29 12:28 ` [PR PATCH] [Closed]: " ahesford
2023-06-29 19:14 ` chrysos349 [this message]
2023-06-29 19:43 ` ahesford
2023-06-29 21:16 ` chrysos349
2023-06-29 22:12 ` ahesford
2023-06-30 2:10 ` sgn
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=20230629191451.N_1juKuzG6WDLRkXnpF-a3cHhpenH1jqQiBPNTMZtNs@z \
--to=chrysos349@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).