From: Randy Barlow <randy@electronsweatshop.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Pseudo up-for-grabs: dev-lang/rust, dev-lang/rust-bin, virtual/rust
Date: Fri, 26 Jan 2024 00:12:10 +0000 [thread overview]
Message-ID: <010f018d431c169d-00a31129-45b2-41dd-9e1c-f5fd6d64c61a-000000@us-east-2.amazonses.com> (raw)
In-Reply-To: <871qa6j9aq.fsf@gentoo.org>
On 1/24/24 23:56, Sam James wrote:
> Please consider stepping forward if you rely on Rust. There's more
> than enough advocates for it, there should be someone who is able
> to then handle the packaging side.
Is this something I could do as a proxy maintainer?
next prev parent reply other threads:[~2024-01-26 0:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 4:56 [gentoo-dev] Pseudo up-for-grabs: dev-lang/rust, dev-lang/rust-bin, virtual/rust Sam James
2024-01-26 0:12 ` Randy Barlow [this message]
2024-01-26 9:15 ` Sam James
2024-01-29 23:37 ` Randy Barlow
2024-01-30 15:40 ` Pascal Jäger
2024-01-31 1:49 ` Randy Barlow
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=010f018d431c169d-00a31129-45b2-41dd-9e1c-f5fd6d64c61a-000000@us-east-2.amazonses.com \
--to=randy@electronsweatshop.com \
--cc=gentoo-dev@lists.gentoo.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