From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
Cc: corbet@lwn.net, ojeda@kernel.org, dirk.behme@de.bosch.com,
alex.gaynor@gmail.com, boqun.feng@gmail.com, gary@garyguo.net,
benno.lossin@proton.me, a.hindborg@samsung.com,
aliceryhl@google.com, workflows@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org, bilbao@vt.edu
Subject: Re: [PATCH v3] kernel-docs: Add new section for Rust learning materials
Date: Tue, 1 Oct 2024 22:10:24 +0200 [thread overview]
Message-ID: <CANiq72=MnCfj_y_dSPZ4Mwyxq1WnuPmw-FQ0H8THLS6kZ8fNOA@mail.gmail.com> (raw)
In-Reply-To: <20240922160411.274949-1-carlos.bilbao.osdev@gmail.com>
On Sun, Sep 22, 2024 at 6:04 PM Carlos Bilbao
<carlos.bilbao.osdev@gmail.com> wrote:
>
> + * Title: **Experiment: Improving the Rust Book**
> +
> + :Author: Cognitive Engineering Lab at Brown University
> + :URL: https://rust-book.cs.brown.edu/
> + :Date: Accessed Sep 22 2024
> + :Keywords: rust, blog.
> + :Description: From the website: "The goal of this experiment is to
> + evaluate and improve the content of the Rust Book to help people
> + learn Rust more effectively.".
Perhaps this could go closer to the Rust book entry since it is a variant of it.
Or are these sorted in a particular way?
> + * Title: **Opsem-team** (repository)
> +
> + :Author: Operational semantics team
> + :URL: https://github.com/rust-lang/opsem-team/tree/main
Nit: I think you can remove the `/tree/main` part of the URL to simplify.
> + :Date: Accessed Sep 22 2024
Since these are repositories, and elsewhere you say "rolling version",
should that one have a concrete date, or should some of these ones
have a rolling date too?
One more that I remembered and that we could have here if we have
other videos/podcasts/... is Crust of Rust (and probably the book from
the same author).
In any case, I think it looks good, thanks!
Acked-by: Miguel Ojeda <ojeda@kernel.org>
Cheers,
Miguel
next prev parent reply other threads:[~2024-10-01 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-22 16:04 Carlos Bilbao
2024-10-01 20:10 ` Miguel Ojeda [this message]
2024-10-07 17:20 ` Jonathan Corbet
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='CANiq72=MnCfj_y_dSPZ4Mwyxq1WnuPmw-FQ0H8THLS6kZ8fNOA@mail.gmail.com' \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bilbao@vt.edu \
--cc=boqun.feng@gmail.com \
--cc=carlos.bilbao.osdev@gmail.com \
--cc=corbet@lwn.net \
--cc=dirk.behme@de.bosch.com \
--cc=gary@garyguo.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=workflows@vger.kernel.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