From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] broot: update to 1.18.0
Date: Sun, 15 Jan 2023 03:30:46 +0100 [thread overview]
Message-ID: <20230115023046.nOlcZH6nG3JH1mFW-sDcVKwVF85FeFrnZVAfdrViboM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41233@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 281 bytes --]
New review comment by cinerea0 on void-packages repository
https://github.com/void-linux/void-packages/pull/41233#discussion_r1070482971
Comment:
1.19 requires Rust 1.65. I've reported it in the [tracking issue](https://github.com/void-linux/void-packages/issues/40805) as well.
next prev parent reply other threads:[~2023-01-15 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 2:42 [PR PATCH] " cinerea0
2023-01-14 1:27 ` [PR REVIEW] " classabbyamp
2023-01-15 2:30 ` cinerea0 [this message]
2023-01-15 2:43 ` classabbyamp
2023-01-15 2:44 ` [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=20230115023046.nOlcZH6nG3JH1mFW-sDcVKwVF85FeFrnZVAfdrViboM@z \
--to=cinerea0@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).