From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ci: add step to verify the functionality of update-check
Date: Sat, 08 Jul 2023 22:52:26 +0200 [thread overview]
Message-ID: <20230708205226.QXKkZ2XT4qR_yX8Wei6SReu85mtxP80LlX0LOCQp6Mc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44927@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 284 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/pull/44927#issuecomment-1627487040
Comment:
I didn't knew about _log.txt, thanks.
Shouldn't this go into lint job rather than x86_64 build?
Ack overall for checking new packages.
next prev parent reply other threads:[~2023-07-08 20:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 19:07 [PR PATCH] " classabbyamp
2023-07-08 19:22 ` Chocimier
2023-07-08 19:56 ` [PR PATCH] [Updated] " classabbyamp
2023-07-08 19:56 ` classabbyamp
2023-07-08 19:58 ` [PR PATCH] [Updated] " classabbyamp
2023-07-08 20:19 ` classabbyamp
2023-07-08 20:26 ` classabbyamp
2023-07-08 20:45 ` classabbyamp
2023-07-08 20:52 ` Chocimier [this message]
2023-07-08 20:55 ` classabbyamp
2023-07-08 21:01 ` classabbyamp
2023-07-08 21:04 ` classabbyamp
2023-07-08 21:09 ` [PR REVIEW] " mhmdanas
2023-07-08 21:11 ` [PR PATCH] [Updated] " classabbyamp
2023-07-08 23:02 ` classabbyamp
2023-07-09 6:35 ` classabbyamp
2023-09-06 0:49 ` classabbyamp
2023-09-06 0:50 ` classabbyamp
2023-09-06 0:51 ` classabbyamp
2023-09-06 0:54 ` classabbyamp
2023-09-06 0:56 ` classabbyamp
2023-09-06 0:58 ` classabbyamp
2023-09-06 1:00 ` classabbyamp
2023-09-06 1:00 ` [PR PATCH] [Updated] " classabbyamp
2023-09-08 8:33 ` [PR PATCH] [Merged]: " classabbyamp
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=20230708205226.QXKkZ2XT4qR_yX8Wei6SReu85mtxP80LlX0LOCQp6Mc@z \
--to=chocimier@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).