From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Add RISC-V toolchain
Date: Thu, 07 Jul 2022 04:14:05 +0200 [thread overview]
Message-ID: <20220707021405.19ETyz9yZgaOvQcMDFbyOxDVay9UQmMQ9Uxot11xub4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35074@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 527 bytes --]
Closed issue by KSPAtlas on void-packages repository
https://github.com/void-linux/void-packages/issues/35074
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname:
Void 5.15.12_1 x86_64 GenuineIntel uptodate rrrmFFFF
* package:
maybe `cross-riscv64-linux-gnu`?
### Expected behavior
### Actual behavior
### Steps to reproduce the behavior
prev parent reply other threads:[~2022-07-07 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-15 21:22 [ISSUE] " KSPAtlas
2022-01-16 9:43 ` Anachron
2022-06-22 2:14 ` github-actions
2022-07-07 2:14 ` github-actions [this message]
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=20220707021405.19ETyz9yZgaOvQcMDFbyOxDVay9UQmMQ9Uxot11xub4@z \
--to=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).