mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: Conor Dooley <conor@kernel.org>,
	sbranden@broadcom.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Move from git://github.com to https://github.com
Date: Thu, 13 Oct 2022 14:12:16 -0700	[thread overview]
Message-ID: <4ce08aac-fda0-0db1-14e5-1d45d4421342@gmail.com> (raw)
In-Reply-To: <mhng-216dc4fc-3a64-4ccb-b428-bbb13ce30199@palmer-ri-x1c9a>

On 10/13/22 12:38, Palmer Dabbelt wrote:
> On Thu, 13 Oct 2022 11:20:51 PDT (-0700), f.fainelli@gmail.com wrote:
>> On 10/13/22 10:02, Conor Dooley wrote:
>>> 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?
>>
>> Yes this should be updated to the stblinux repository, thanks! If you
>> want to split on a per-maintainer basis, I can take the Broadcom entries
>> separately  through the Broadcom ARM SoC pull request, else:
>>
>> Acked-by: Florian Fainelli <f.fainelli@gmail.com>
> 
> I'll split them up and send a v2.

It is fine either way with me, up to you.
-- 
Florian

      reply	other threads:[~2022-10-13 21:12 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
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 [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=4ce08aac-fda0-0db1-14e5-1d45d4421342@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=conor@kernel.org \
    --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®