From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
linux-doc@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org, patches@lists.linux.dev
Subject: Re: [PATCH] docs: rust: point directly to the standalone installers
Date: Mon, 6 Mar 2023 23:24:35 +0100 [thread overview]
Message-ID: <CANiq72kF1wy0HWTPFaF3UKOvoZ19kdWe_mCAt8KxY9364-RE-w@mail.gmail.com> (raw)
In-Reply-To: <20230306220959.240235-1-ojeda@kernel.org>
On Mon, Mar 6, 2023 at 11:10 PM Miguel Ojeda <ojeda@kernel.org> wrote:
>
> Thus point directly to the page (and anchor) with the table that
> contains the standalone installers (plus signing key etc.).
By the way, while it is fairly easy to figure out the links to
previous stable releases, it would nevertheless be nice to have a way
to show them. At least there is a `FIXME` comment in those docs about
it:
https://github.com/rust-lang/rust-forge/blob/793249870cf7610ffe78dcb9c7acc7efdbbcc713/src/infra/other-installation-methods.md?plain=1#L99-L101
So I opened https://github.com/rust-lang/rust-forge/issues/676.
Cheers,
Miguel
next prev parent reply other threads:[~2023-03-06 22:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 22:09 [PATCH] docs: rust: point directly to the standalone installers Miguel Ojeda
2023-03-06 22:24 ` Miguel Ojeda [this message]
2023-03-07 9:26 ` Vincenzo Palazzo
2023-03-07 12:29 ` Andreas Hindborg
2023-03-07 12:45 ` Miguel Ojeda
2023-05-31 17:05 ` Miguel Ojeda
2023-05-31 17:05 ` Miguel Ojeda
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=CANiq72kF1wy0HWTPFaF3UKOvoZ19kdWe_mCAt8KxY9364-RE-w@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=gary@garyguo.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
/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).