linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
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, 02 Jul 2025 09:41:15 -0600	[thread overview]
Message-ID: <87ikkapplw.fsf@trenco.lwn.net> (raw)
In-Reply-To: <02ffd0a2-3036-475c-9e23-55d706eec7ea@gmail.com>

Xose Vazquez Perez <xose.vazquez@gmail.com> writes:

> 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:

Why are we concerned about consistency here?

As you will have observed with your other patch, wholesale changes to a
file like MAINTAINERS lead to merge conflicts.  We can handle those - if
there is a good reason.  I'm not convinced that "consistency" counts as
such.  Let's just let the maintainers present their trees as they wish.

Thanks,

jon

  reply	other threads:[~2025-07-02 15:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25 14:20 [PATCH] MAINTAINERS: standardize git.kernel.org URLs Xose Vazquez Perez
2025-06-25 17:27 ` Jonathan Corbet
2025-07-02 15:32   ` Xose Vazquez Perez
2025-07-02 15:41     ` Jonathan Corbet [this message]
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=87ikkapplw.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xose.vazquez@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;
as well as URLs for NNTP newsgroup(s).