From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
DOC ML <linux-doc@vger.kernel.org>,
KERNEL ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: standardize git.kernel.org URLs
Date: Wed, 2 Jul 2025 17:32:55 +0200 [thread overview]
Message-ID: <02ffd0a2-3036-475c-9e23-55d706eec7ea@gmail.com> (raw)
In-Reply-To: <87a55vag0l.fsf@trenco.lwn.net>
On 6/25/25 7:27 PM, Jonathan Corbet wrote:
> Xose Vazquez Perez <xose.vazquez@gmail.com> writes:
>
>> replace https: with git:, delete trailing /, and identify repos as "git"
>>
>> Cc: Jonathan Corbet <corbet@lwn.net> (maintainer:DOCUMENTATION)
>> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> Cc: DOC ML <linux-doc@vger.kernel.org> (open list:DOCUMENTATION)
>> Cc: KERNEL ML <linux-kernel@vger.kernel.org> (open list)
>> Signed-off-by: Xose Vazquez Perez <xose.vazquez@gmail.com>
>> ---
>> MAINTAINERS | 50 +++++++++++++++++++++++++-------------------------
>> 1 file changed, 25 insertions(+), 25 deletions(-)
> So ... we're changing GitHub URLs from git: to https:, and Gitlab URLs
> from https: to git:?
>
> Certainly we want to fix URLs that are broken, but is there any real
> reason to churn up the MAINTAINERS file to "fix" URLs that work?
The reason was to be *consistent* with the rest of the entries.
Because most of them(380) are using git:, vs 22 for https:
$ grep git.kernel.org MAINTAINERS | sed 's#://#:// #' | awk '{print $3}' | sort | uniq -c | sort -n
1 git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git
22 https://
380 git://
But Greg has some concerns about this protocol:
https://lore.kernel.org/lkml/2025062654-lubricant-lettuce-3405@gregkh/
"This bypasses the mirror systems in place with the https: protocol,
please do not do this without a lot of justification and agreement of
the hosting providers involved as they will have a large increase in
resources if this were to change."
So, the right patch should replace git://git.kernel.org with https://git.kernel.org in all the tree.
$ git grep -l "git://git.kernel.org"
Documentation/admin-guide/LSM/apparmor.rst
Documentation/admin-guide/kdump/kdump.rst
Documentation/admin-guide/reporting-issues.rst
Documentation/admin-guide/workload-tracing.rst
Documentation/arch/arm/keystone/knav-qmss.rst
Documentation/dev-tools/sparse.rst
Documentation/filesystems/bcachefs/SubmittingPatches.rst
Documentation/filesystems/erofs.rst
Documentation/filesystems/f2fs.rst
Documentation/maintainer/pull-requests.rst
Documentation/mm/hwpoison.rst
Documentation/process/adding-syscalls.rst
Documentation/process/maintainer-kvm-x86.rst
Documentation/process/submitting-patches.rst
Documentation/sound/hd-audio/notes.rst
Documentation/timers/no_hz.rst
Documentation/translations/it_IT/process/adding-syscalls.rst
Documentation/translations/it_IT/process/submitting-patches.rst
Documentation/translations/sp_SP/process/adding-syscalls.rst
Documentation/translations/sp_SP/process/maintainer-kvm-x86.rst
Documentation/translations/sp_SP/process/submitting-patches.rst
Documentation/translations/zh_CN/admin-guide/reporting-issues.rst
Documentation/translations/zh_CN/dev-tools/sparse.rst
Documentation/translations/zh_CN/how-to.rst
Documentation/translations/zh_CN/maintainer/pull-requests.rst
Documentation/translations/zh_CN/mm/hwpoison.rst
Documentation/translations/zh_CN/process/submitting-patches.rst
Documentation/translations/zh_TW/admin-guide/reporting-issues.rst
Documentation/translations/zh_TW/dev-tools/sparse.rst
Documentation/translations/zh_TW/process/submitting-patches.rst
MAINTAINERS
drivers/net/wireless/intel/iwlwifi/iwl-drv.c
scripts/get_maintainer.pl
scripts/package/debian/copyright
tools/tracing/rtla/README.txt
tools/usb/usbip/src/usbip.c
tools/verification/rv/README.txt
next prev parent reply other threads:[~2025-07-02 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 14:20 Xose Vazquez Perez
2025-06-25 17:27 ` Jonathan Corbet
2025-07-02 15:32 ` Xose Vazquez Perez [this message]
2025-07-02 15:41 ` Jonathan Corbet
2025-06-26 7:38 ` Greg Kroah-Hartman
2025-06-26 8:06 ` Xose Vazquez Perez
2025-06-26 8:20 ` Conor Dooley
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=02ffd0a2-3036-475c-9e23-55d706eec7ea@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®