Linux Test Project
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@rivosinc.com>
To: vapier@gentoo.org, chrubis@suse.cz, wanlong.gao@gmail.com,
	jstancek@redhat.com,  stanislav.kholmanskikh@oracle.com,
	alexey.kodanev@oracle.com, ltp@lists.linux.it
Cc: Conor Dooley <conor.dooley@microchip.com>,
	linux-kernel@vger.kernel.org,
	Palmer Dabbelt <palmer@rivosinc.com>
Subject: [LTP] [PATCH] MAINTAINERS: git://github -> https://github.com for linux-test-project
Date: Thu, 13 Oct 2022 14:46:38 -0700	[thread overview]
Message-ID: <20221013214638.30953-1-palmer@rivosinc.com> (raw)

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 d103b44fb40c..d118acdce8b8 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -11972,7 +11972,7 @@ M:	Alexey Kodanev <alexey.kodanev@oracle.com>
 L:	ltp@lists.linux.it (subscribers-only)
 S:	Maintained
 W:	http://linux-test-project.github.io/
-T:	git git://github.com/linux-test-project/ltp.git
+T:	git https://github.com/linux-test-project/ltp.git
 
 LYNX 28G SERDES PHY DRIVER
 M:	Ioana Ciornei <ioana.ciornei@nxp.com>
-- 
2.38.0


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

             reply	other threads:[~2022-10-14  7:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-13 21:46 Palmer Dabbelt [this message]
2022-10-14  9:05 ` [LTP] [PATCH] MAINTAINERS: git://github -> https://github.com for linux-test-project Cyril Hrubis
2022-10-14  9:20 ` Petr Vorel
2022-10-17 15:20 ` Petr Vorel

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=20221013214638.30953-1-palmer@rivosinc.com \
    --to=palmer@rivosinc.com \
    --cc=alexey.kodanev@oracle.com \
    --cc=chrubis@suse.cz \
    --cc=conor.dooley@microchip.com \
    --cc=jstancek@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltp@lists.linux.it \
    --cc=stanislav.kholmanskikh@oracle.com \
    --cc=vapier@gentoo.org \
    --cc=wanlong.gao@gmail.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