From: TinfoilSubmarine <TinfoilSubmarine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Rust 1.76
Date: Sat, 10 Feb 2024 16:39:52 +0100 [thread overview]
Message-ID: <20240210153952.39073222E5@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48634@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 267 bytes --]
New comment by TinfoilSubmarine on void-packages repository
https://github.com/void-linux/void-packages/pull/48634#issuecomment-1937046367
Comment:
`conduit` failure isn't caused by 1.76, I can reproduce when building it with 1.75 on my machine. Looking into it...
next prev parent reply other threads:[~2024-02-10 15:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 2:13 [PR PATCH] " tranzystorekk
2024-02-10 11:13 ` tranzystorekk
2024-02-10 11:35 ` [PR PATCH] [Updated] " tranzystorekk
2024-02-10 11:56 ` tranzystorekk
2024-02-10 15:35 ` wpbirney
2024-02-10 15:39 ` TinfoilSubmarine [this message]
2024-02-10 15:42 ` tranzystorekk
2024-02-14 21:01 ` classabbyamp
2024-02-14 22:54 ` tranzystorekk
2024-02-15 11:53 ` tranzystorekk
2024-02-15 11:54 ` tranzystorekk
2024-02-17 11:56 ` [PR PATCH] [Updated] " tranzystorekk
2024-02-24 7:18 ` [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=20240210153952.39073222E5@inbox.vuxu.org \
--to=tinfoilsubmarine@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).