mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Palmer Dabbelt <palmer@rivosinc.com>,
	jfs-discussion@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org, Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH] MAINTAINERS: git://github -> https://github.com for kleikamp
Date: Mon, 17 Oct 2022 15:10:32 -0500	[thread overview]
Message-ID: <6f08c2c8-45bd-47e1-0835-281abd60f242@oracle.com> (raw)
In-Reply-To: <20221013214638.30994-1-palmer@rivosinc.com>

Applied.

Thanks,
Shaggy

On 10/13/22 4:46PM, Palmer Dabbelt 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 6a4e8144198b..9a47bd58a330 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -10867,7 +10867,7 @@ M:	Dave Kleikamp <shaggy@kernel.org>
>   L:	jfs-discussion@lists.sourceforge.net
>   S:	Maintained
>   W:	http://jfs.sourceforge.net/
> -T:	git git://github.com/kleikamp/linux-shaggy.git
> +T:	git https://github.com/kleikamp/linux-shaggy.git
>   F:	Documentation/admin-guide/jfs.rst
>   F:	fs/jfs/
>   

      reply	other threads:[~2022-10-17 21:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13 21:46 Palmer Dabbelt
2022-10-17 20:10 ` Dave Kleikamp [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=6f08c2c8-45bd-47e1-0835-281abd60f242@oracle.com \
    --to=dave.kleikamp@oracle.com \
    --cc=conor.dooley@microchip.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --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®