From: tranzystorek-io <tranzystorek-io@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Update Rust toolchain to 1.60.0
Date: Fri, 20 May 2022 08:52:52 +0200 [thread overview]
Message-ID: <20220520065252.Xy1YfcjPy4JqPpggBQVAQtMaYkGkD49R0br78GyI-Jw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36269@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 260 bytes --]
New comment by tranzystorek-io on void-packages repository
https://github.com/void-linux/void-packages/pull/36269#issuecomment-1132538697
Comment:
I wanted to take a stab at this, but I'm not sure where to look for patches, I'd appreciate some pointers 😄
next prev parent reply other threads:[~2022-05-20 6:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 19:49 [PR PATCH] [DRAFT][ci skip] Update Rust toolchain to 1.59.0 subnut
2022-03-22 2:23 ` [PR PATCH] [Updated] " subnut
2022-03-22 2:52 ` subnut
2022-03-22 2:53 ` subnut
2022-03-22 3:36 ` [PR PATCH] [Updated] " subnut
2022-03-22 3:44 ` subnut
2022-03-22 4:17 ` subnut
2022-03-22 4:18 ` subnut
2022-03-22 4:19 ` subnut
2022-03-22 4:33 ` [PR PATCH] [Updated] [DRAFT] " subnut
2022-03-22 4:34 ` subnut
2022-03-22 6:56 ` subnut
2022-03-22 7:09 ` subnut
2022-03-22 7:10 ` subnut
2022-03-22 11:59 ` [PR PATCH] [Updated] " subnut
2022-03-22 12:01 ` subnut
2022-03-22 13:26 ` subnut
2022-03-22 15:06 ` subnut
2022-03-23 3:54 ` subnut
2022-03-28 3:38 ` subnut
2022-04-16 14:53 ` subnut
2022-04-16 17:25 ` q66
2022-04-16 19:25 ` [PR PATCH] [Updated] " subnut
2022-04-16 20:04 ` subnut
2022-04-17 3:10 ` subnut
2022-04-17 3:35 ` subnut
2022-04-17 17:07 ` subnut
2022-04-17 17:07 ` [PR PATCH] [Closed]: " subnut
2022-04-17 17:08 ` subnut
2022-04-28 12:19 ` Update Rust toolchain to 1.60.0 tranzystorek-io
2022-05-19 23:01 ` cinerea0
2022-05-20 5:39 ` [PR PATCH] [Closed]: " subnut
2022-05-20 5:39 ` subnut
2022-05-20 5:39 ` subnut
2022-05-20 6:52 ` tranzystorek-io [this message]
2022-05-20 9:38 ` subnut
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=20220520065252.Xy1YfcjPy4JqPpggBQVAQtMaYkGkD49R0br78GyI-Jw@z \
--to=tranzystorek-io@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).