linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Martin Rodriguez Reboredo <yakoyoku@gmail.com>
Cc: ojeda@kernel.org, alex.gaynor@gmail.com, benno.lossin@proton.me,
	bjorn3_gh@protonmail.com, boqun.feng@gmail.com, gary@garyguo.net,
	gyakovlev@gentoo.org, jan.steffens@gmail.com, jistone@redhat.com,
	linux-kernel@vger.kernel.org, patches@lists.linux.dev,
	rust-for-linux@vger.kernel.org, wedsonaf@gmail.com,
	william.brown@suse.com
Subject: Re: [PATCH 3/3] rust: upgrade to Rust 1.68.2
Date: Wed, 31 May 2023 23:30:53 +0200	[thread overview]
Message-ID: <CANiq72nm8DQECm0CRjCSyzjPQK+z44_LHpanjTVv9mWRvYqVPw@mail.gmail.com> (raw)
In-Reply-To: <22ac8a99-d243-c537-41c7-ff2c5e69d28f@gmail.com>

On Wed, May 31, 2023 at 9:48 PM Martin Rodriguez Reboredo
<yakoyoku@gmail.com> wrote:
>
> 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]

Thanks! There is also "comparing releases" [1], but it does not seem
to allow to restrict to a folder... :(

A dedicated view where one could navigate everything between two
points (or at least two releases), including PRs, content diff,
commits, closed issues, etc.; and being able to restrict it to
particular folders would be great.

[1] https://docs.github.com/en/repositories/releasing-projects-on-github/comparing-releases

Cheers,
Miguel

  parent reply	other threads:[~2023-05-31 21:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18 21:43 [PATCH 0/3] Rust 1.68.2 upgrade Miguel Ojeda
2023-04-18 21:43 ` [PATCH 1/3] rust: alloc: clarify what is the upstream version Miguel Ojeda
2023-04-19  2:51   ` Martin Rodriguez Reboredo
2023-04-19  8:06   ` Benno Lossin
2023-04-19 11:58   ` Gary Guo
2023-04-20 12:14   ` Björn Roy Baron
2023-04-18 21:43 ` [PATCH 2/3] rust: arc: fix intra-doc link in `Arc<T>::init` Miguel Ojeda
2023-04-19  2:51   ` Martin Rodriguez Reboredo
2023-04-19  8:11   ` Benno Lossin
2023-04-19 11:59   ` Gary Guo
2023-04-20 12:15   ` Björn Roy Baron
2023-04-18 21:43 ` [PATCH 3/3] rust: upgrade to Rust 1.68.2 Miguel Ojeda
2023-04-19  3:02   ` Martin Rodriguez Reboredo
2023-05-31 17:02     ` Miguel Ojeda
     [not found]       ` <22ac8a99-d243-c537-41c7-ff2c5e69d28f@gmail.com>
2023-05-31 21:30         ` Miguel Ojeda [this message]
2023-04-19 12:38   ` Gary Guo
2023-04-20 12:31   ` Björn Roy Baron
2023-04-18 22:17 ` [PATCH 0/3] Rust 1.68.2 upgrade Miguel Ojeda
2023-04-20  3:23 ` Boqun Feng
2023-04-20  3:45 ` David Gow
2023-04-20 13:12 ` Ariel Miculas
2023-04-20 13:19   ` Miguel Ojeda
2023-04-20 17:17     ` Ariel Miculas
2023-04-20 17:20       ` Miguel Ojeda
2023-05-04 22:27         ` Fabien Parent
2023-05-05  9:59           ` Miguel Ojeda
2023-05-31 17:03 ` 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=CANiq72nm8DQECm0CRjCSyzjPQK+z44_LHpanjTVv9mWRvYqVPw@mail.gmail.com \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=alex.gaynor@gmail.com \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=gary@garyguo.net \
    --cc=gyakovlev@gentoo.org \
    --cc=jan.steffens@gmail.com \
    --cc=jistone@redhat.com \
    --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 \
    --cc=william.brown@suse.com \
    --cc=yakoyoku@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).