All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Joe Perches <joe@perches.com>
Cc: Sasha Levin <sashal@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] get_maintainer: lazy load JSON::PP only when --json is used
Date: Sat, 31 Oct 2026 01:11:13 +0100	[thread overview]
Message-ID: <auUyIX3BYZ26iaBY@redhat.com> (raw)
In-Reply-To: <d3e29969aeaf10b654a3be87601adee6be89c9d6.camel@perches.com>

On 10/30, Joe Perches wrote:
>
> On Sat, 2026-10-31 at 00:35 +0100, Oleg Nesterov wrote:
> > On 10/30, Joe Perches wrote:
> > >
> > > I think that was added in Linus' 7.2 in mid August and in -next since April
> >
> > Yes, I hit this problem months ago, but didn't have time to send the fix.
>
> Nor apparently have time to send an email to the get_maintainer
> maintainer about it either.

No. I knew that this problem is trivial and I can send the trivial fix
when I have time to check the code and write the changelog.

> > Great, then perhaps you can ACK my trivial patch? Then we can discuss
> > the possible improvements.
>
> Maybe when it's done without needing updates.

Sorry, I don't understand...

> In the meantime, you have an easy workaround with dnf install perl-core.

Sure. Or I guess I can install perl-JSON-PP.noarch... most probably this
is the necessary module.

OK. So in essence you NACK this change. OK, maintainer is always right.
I won't argue even if I don't understand why you dislike this trivial change.
Afaics it can't make any regression, it just allows to continue to use
get_maintainer.pl without JSON::PP, as it was always possible.

Oleg.


  reply	other threads:[~2026-10-31  0:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 15:43 [PATCH] get_maintainer: lazy load JSON::PP only when --json is used Oleg Nesterov
2026-10-30 16:07 ` Joe Perches
2026-10-30 16:17   ` Oleg Nesterov
2026-10-30 16:32     ` Joe Perches
2026-10-30 21:44       ` Oleg Nesterov
2026-10-30 22:18         ` Sasha Levin
2026-10-30 22:19         ` Joe Perches
2026-10-30 22:55           ` Oleg Nesterov
2026-10-30 23:17             ` Joe Perches
2026-10-30 23:35               ` Oleg Nesterov
2026-10-30 23:54                 ` Joe Perches
2026-10-31  0:11                   ` Oleg Nesterov [this message]
2026-10-30 16:29 ` [PATCH v2] " Oleg Nesterov

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=auUyIX3BYZ26iaBY@redhat.com \
    --to=oleg@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.