From: daniel-eys <daniel-eys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] podman: update to 3.4.4.
Date: Sat, 11 Dec 2021 15:13:51 +0100 [thread overview]
Message-ID: <20211211141351.6N7KDw6EeIrA0pxKikb_nxgUxkS9ZTGitFCfqbF3Voo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34465@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 193 bytes --]
New comment by daniel-eys on void-packages repository
https://github.com/void-linux/void-packages/pull/34465#issuecomment-991658044
Comment:
Patch imported and musl builds seem fine again.
next prev parent reply other threads:[~2021-12-11 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 10:52 [PR PATCH] " daniel-eys
2021-12-10 11:16 ` daniel-eys
2021-12-10 11:20 ` [WIP] " daniel-eys
2021-12-10 19:08 ` ericonr
2021-12-11 14:08 ` [PR PATCH] [Updated] " daniel-eys
2021-12-11 14:13 ` daniel-eys [this message]
2021-12-16 23:19 ` daniel-eys
2021-12-16 23:19 ` [PR PATCH] [Closed]: " daniel-eys
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=20211211141351.6N7KDw6EeIrA0pxKikb_nxgUxkS9ZTGitFCfqbF3Voo@z \
--to=daniel-eys@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).