From: Conor Dooley <conor@kernel.org>
To: Palmer Dabbelt <palmer@rivosinc.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Scott Branden <sbranden@broadcom.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Move from git://github.com to https://github.com
Date: Thu, 13 Oct 2022 18:02:47 +0100 [thread overview]
Message-ID: <Y0hEt51q+Fs0ICbB@spud> (raw)
In-Reply-To: <20221013153258.28228-1-palmer@rivosinc.com>
On Thu, Oct 13, 2022 at 08:32:58AM -0700, Palmer Dabbelt wrote:
> Github deprecated the git:// links about a year ago, but it looks like
> there's still a handful of them in the MAINTAINERS file. Conor pointed
> this out about the RISC-V KVM tree, but I figured it'd be better to just
> fix them all -- I've got a bunch of insteadOf so I didn't even notice
> the deprecation, but new contributors probably don't and might get a bit
> confused.
>
> Reported-by: Conor Dooley <conor@kernel.org>
> Link: https://github.blog/2021-09-01-improving-git-protocol-security-github/
> Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
> ---
> @@ -3990,7 +3990,7 @@ M: Ray Jui <rjui@broadcom.com>
> M: Scott Branden <sbranden@broadcom.com>
> R: Broadcom internal kernel review list <bcm-kernel-feedback-list@broadcom.com>
> S: Maintained
> -T: git git://github.com/broadcom/mach-bcm
> +T: git https://github.com/broadcom/mach-bcm
This link is dead, I can't find a repo with that name on their GitHub
profile.
@Florian, should this be updated to the stblinux repo instead?
> F: arch/arm/mach-bcm/
> N: bcm281*
> N: bcm113*
> @@ -4055,7 +4055,7 @@ M: Florian Fainelli <f.fainelli@gmail.com>
> R: Broadcom internal kernel review list <bcm-kernel-feedback-list@broadcom.com>
> L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> S: Maintained
> -T: git git://github.com/broadcom/stblinux.git
> +T: git https://github.com/broadcom/stblinux.git
> F: Documentation/devicetree/bindings/pci/brcm,stb-pcie.yaml
> F: arch/arm/boot/dts/bcm7*.dts*
> F: arch/arm/include/asm/hardware/cache-b15-rac.h
Other than that, I clicked all the links - some look dead but that's not
the point of this patch..
Tested-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
next prev parent reply other threads:[~2022-10-13 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 15:32 Palmer Dabbelt
2022-10-13 17:02 ` Conor Dooley [this message]
2022-10-13 17:08 ` Conor Dooley
2022-10-13 17:10 ` Palmer Dabbelt
2022-10-13 18:20 ` Florian Fainelli
2022-10-13 19:38 ` Palmer Dabbelt
2022-10-13 21:12 ` Florian Fainelli
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=Y0hEt51q+Fs0ICbB@spud \
--to=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=palmer@rivosinc.com \
--cc=sbranden@broadcom.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®