From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: fragments: update to 2.1
Date: Wed, 01 Feb 2023 00:00:53 +0100 [thread overview]
Message-ID: <20230131230053.ozYrmAtlUOO9D34FhxSNFhWurlYvex112j988BYUtzI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41459@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/pull/41459#issuecomment-1411186444
Comment:
> That fixed it! The solution here appears to apply to all rust programs using meson that are hosted on the Gnome GitLab instance.
Thanks! That solution will also be helpful for other rust packages
next prev parent reply other threads:[~2023-01-31 23:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 2:07 [PR PATCH] " cinerea0
2023-01-11 22:57 ` paper42
2023-01-31 2:27 ` [PR PATCH] [Updated] " cinerea0
2023-01-31 2:46 ` cinerea0
2023-01-31 3:32 ` cinerea0
2023-01-31 23:00 ` paper42 [this message]
2023-01-31 23:01 ` [PR PATCH] [Merged]: " paper42
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=20230131230053.ozYrmAtlUOO9D34FhxSNFhWurlYvex112j988BYUtzI@z \
--to=paper42@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).