From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: william.zhang@broadcom.com, anand.gore@broadcom.com,
kursad.oney@broadcom.com, f.fainelli@gmail.com,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org, linux-mips@vger.kernel.org,
rjui@broadcom.com, sbranden@broadcom.com, rafal@milecki.pl,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH] MAINTAINERS: git://github -> https://github.com for broadcom
Date: Mon, 17 Oct 2022 00:48:43 +0200 [thread overview]
Message-ID: <CAAdtpL5eFu9Vh4Xnkm5CPGb_h5HTe7M+WiG46t3d5gFu6b9ZEQ@mail.gmail.com> (raw)
In-Reply-To: <20221013214639.31074-1-palmer@rivosinc.com>
On Thu, Oct 13, 2022 at 11:50 PM 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 | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
next prev parent reply other threads:[~2022-10-16 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 21:46 [PATCH] MAINTAINERS: git://github -> https://github.com for broadcom Palmer Dabbelt
2022-10-14 0:41 ` William Zhang
2022-10-16 22:48 ` Philippe Mathieu-Daudé [this message]
2022-10-17 17:38 ` 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=CAAdtpL5eFu9Vh4Xnkm5CPGb_h5HTe7M+WiG46t3d5gFu6b9ZEQ@mail.gmail.com \
--to=f4bug@amsat.org \
--cc=anand.gore@broadcom.com \
--cc=conor.dooley@microchip.com \
--cc=f.fainelli@gmail.com \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=palmer@rivosinc.com \
--cc=rafal@milecki.pl \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=william.zhang@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;
as well as URLs for NNTP newsgroup(s).