From: Alex Williamson <alex.williamson@redhat.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH] MAINTAINERS: git://github -> https://github.com for awilliam
Date: Thu, 10 Nov 2022 13:16:40 -0700 [thread overview]
Message-ID: <20221110131640.6e00811f.alex.williamson@redhat.com> (raw)
In-Reply-To: <20221013214636.30721-1-palmer@rivosinc.com>
On Thu, 13 Oct 2022 14:46:36 -0700
Palmer Dabbelt <palmer@rivosinc.com> wrote:
> Github deprecated the git:// links about a year ago, so let's move to
> the https:// URLs instead.
>
> Reported-by: Conor Dooley <conor.dooley@microchip.com>
> Link: https://github.blog/2021-09-01-improving-git-protocol-security-github/
> Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
> ---
> I've split these up by github username so folks can take them
> independently, as some of these repos have been renamed at github and
> thus need more than just a sed to fix them.
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 3705c487450b..41a925931cc3 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -21305,7 +21305,7 @@ M: Alex Williamson <alex.williamson@redhat.com>
> R: Cornelia Huck <cohuck@redhat.com>
> L: kvm@vger.kernel.org
> S: Maintained
> -T: git git://github.com/awilliam/linux-vfio.git
> +T: git https://github.com/awilliam/linux-vfio.git
> F: Documentation/driver-api/vfio.rst
> F: drivers/vfio/
> F: include/linux/vfio.h
Applied to vfio next branch for v6.2. Thanks,
Alex
prev parent reply other threads:[~2022-11-10 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 21:46 Palmer Dabbelt
2022-10-17 20:32 ` Philippe Mathieu-Daudé
2022-11-10 20:16 ` Alex Williamson [this message]
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=20221110131640.6e00811f.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=conor.dooley@microchip.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=palmer@rivosinc.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
all inboxes | Powered by JetHome®