From: enderger <enderger@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package lib3mf
Date: Thu, 03 Nov 2022 00:46:26 +0100 [thread overview]
Message-ID: <20221102234626._pUkxQ2sC9fX0hI6GISd8BeIucv0ttoWQNRZNbca1-Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40307@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
New comment by enderger on void-packages repository
https://github.com/void-linux/void-packages/pull/40307#issuecomment-1301498316
Comment:
@paper42 - Sorry for any confusion, I pushed another commit during the CI run so it does actually need to run again. This time, I've ensured that the linter passes and the project compiles, so CI should pass this time.
next prev parent reply other threads:[~2022-11-02 23:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 22:13 [PR PATCH] " enderger
2022-11-02 22:49 ` enderger
2022-11-02 22:59 ` [PR REVIEW] " paper42
2022-11-02 23:10 ` [PR PATCH] [Updated] " enderger
2022-11-02 23:10 ` [PR REVIEW] " enderger
2022-11-02 23:15 ` [PR PATCH] [Updated] " enderger
2022-11-02 23:17 ` enderger
2022-11-02 23:23 ` enderger
2022-11-02 23:46 ` enderger [this message]
2022-11-03 0:16 ` [PR REVIEW] " classabbyamp
2022-11-03 0:16 ` classabbyamp
2022-11-03 0:16 ` classabbyamp
2022-11-03 0:16 ` classabbyamp
2022-11-03 0:23 ` enderger
2022-11-03 0:23 ` enderger
2022-11-03 0:23 ` enderger
2022-11-03 0:29 ` enderger
2022-11-03 0:32 ` classabbyamp
2022-11-03 0:48 ` [PR PATCH] [Updated] " enderger
2022-11-03 0:58 ` [PR REVIEW] " enderger
2022-11-03 0:59 ` enderger
2022-11-03 1:12 ` [PR PATCH] [Updated] " enderger
2022-11-03 1:16 ` enderger
2022-11-03 1:32 ` [PR REVIEW] " enderger
2023-02-01 2:07 ` github-actions
2023-02-16 2:01 ` [PR PATCH] [Closed]: " github-actions
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=20221102234626._pUkxQ2sC9fX0hI6GISd8BeIucv0ttoWQNRZNbca1-Y@z \
--to=enderger@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).