From: yoshiyoshyosh <yoshiyoshyosh@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ferium: update to 4.5.0
Date: Tue, 30 Jan 2024 19:37:17 +0100 [thread overview]
Message-ID: <20240130183717.C1A3A29CF0@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48445@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 325 bytes --]
New comment by yoshiyoshyosh on void-packages repository
https://github.com/void-linux/void-packages/pull/48445#issuecomment-1917660748
Comment:
beat me to it, smh.
the musl checks failing seems to just be from the api; just tested the build checks on musl myself and they worked, so there shouldn't be any worry about it
next prev parent reply other threads:[~2024-01-30 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 17:35 [PR PATCH] " SolitudeSF
2024-01-30 18:36 ` yoshiyoshyosh
2024-01-30 18:37 ` yoshiyoshyosh [this message]
2024-01-30 18:43 ` [PR PATCH] [Updated] " SolitudeSF
2024-01-31 16:11 ` [PR PATCH] [Merged]: " ahesford
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=20240130183717.C1A3A29CF0@inbox.vuxu.org \
--to=yoshiyoshyosh@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).