[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <22ac8a99-d243-c537-41c7-ff2c5e69d28f@gmail.com>
Date: Wed, 31 May 2023 16:48:27 -0300
From: Martin Rodriguez Reboredo <yakoyoku@...il.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: ojeda@...nel.org, alex.gaynor@...il.com, benno.lossin@...ton.me,
bjorn3_gh@...tonmail.com, boqun.feng@...il.com, gary@...yguo.net,
gyakovlev@...too.org, jan.steffens@...il.com, jistone@...hat.com,
linux-kernel@...r.kernel.org, patches@...ts.linux.dev,
rust-for-linux@...r.kernel.org, wedsonaf@...il.com,
william.brown@...e.com
Subject: Re: [PATCH 3/3] rust: upgrade to Rust 1.68.2
On 5/31/23 14:02, Miguel Ojeda wrote:
> On Wed, Apr 19, 2023 at 5:02 AM Martin Rodriguez Reboredo
> <yakoyoku@...il.com> wrote:
>>
>> Kinda bunch to review, although may I ask if each time the `alloc`
>> crate is updated is worth to mention the changes upon it [1], can be
>> skipped otherwise.
>>
>> Link: https://github.com/rust-lang/rust/commits/master/library/alloc [1]
>
> That could be nice if we could give a link similar to, say, what:
>
> git log 1.62.0..1.68.2 -- library/alloc/src/
>
> produces (or perhaps a list of PRs) -- is it possible to do so with a
> GitHub URL? If so, please let me know!
>
> Cheers,
> Miguel
It seems that kind of URL comparisons in GitHub aren't supported yet
per the docs say [1]. Sad but maybe in the future they are going to be
supported, or at least I hope GitLab or Gitea do it.
Link: https://docs.github.com/en/pull-requests/committing-changes-to-your-project/viewing-and-comparing-commits/comparing-commits [1]
Powered by blists - more mailing lists