[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72nHmt5_CnLB3+3RopJ+u94pgq1Nk08j0TSk28NZmeoCPg@mail.gmail.com>
Date: Mon, 21 Aug 2023 01:14:02 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Trevor Gross <tmgross@...ch.edu>
Cc: ojeda@...nel.org, alex.gaynor@...il.com, wedsonaf@...il.com,
boqun.feng@...il.com, gary@...yguo.net, bjorn3_gh@...tonmail.com,
benno.lossin@...ton.me, corbet@....net, yakoyoku@...il.com,
aliceryhl@...gle.com, linux-doc@...r.kernel.org,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] docs: rust: update instructions for obtaining
'core' source
On Thu, Aug 3, 2023 at 8:12 AM Trevor Gross <tmgross@...ch.edu> wrote:
>
> This changes the suggested method of obtaining Rust's source to using the
> tarball rather than a full clone, and adds a clarification about 'rustup
> override'.
Applied to `rust-next`, thanks!
In the second patch, I undid the `:` to `::` change -- the latter is
meant to create a literal block.
Cheers,
Miguel
Powered by blists - more mailing lists