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 00:35:15 +0100 [thread overview]
Message-ID: <auUps7Hy7W0SqWw3@redhat.com> (raw)
In-Reply-To: <9ba498189291b99fe18d3a8ac32722495fa3227d.camel@perches.com>
On 10/30, Joe Perches wrote:
>
> On Fri, 2026-10-30 at 23:55 +0100, Oleg Nesterov wrote:
> > > >
> > > > But why? Why make get_maintainer.pl depend on yet another module?
> > > > FYI, on my Fedora 44
> > > >
> > $ perl -we 'use Module::Load::Conditional qw(check_install);'
> > Can't locate Module/Load/Conditional.pm in @INC (you may need to install the Module::Load::Conditional module) (@INC entries checked: /usr/local/lib64/perl5/5.42 /usr/local/share/perl5/5.42 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5) at -e line 1.
> > BEGIN failed--compilation aborted at -e line 1.
> > >
> > > Module::Load is a core perl module since 5.10 and
> > > I think you are using a broken version of a perl installation
> > And how do you think it is broken? my laptop runs the fresh Fedora 44.
>
> It doesn't include perl-core ;)
you can blame the Fedora maintainers, not me ;)
> > I used ./scripts/get_maintainer.pl many years, almost every day, and I never
> > needed to install the additional modules. Until ("get_maintainer: add --json
> > output mode")
>
> 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.
So I had to have "git revert 09d8b39563e84fc245d642182715a7e0e024b0f2" in my
local trees until today.
> > It's not that we disagree... Worse, we can't understand each other :(
> > Perhaps is this my fault.
>
> I don't disagree with the concept of the patch.
Great, then perhaps you can ACK my trivial patch? Then we can discuss
the possible improvements.
> I think we understand each other fine, you just care less about the
> output error message.
Yes, it is true in that I don't really care about the output error message.
But then again. This error message can only happen if JSON::PP is not
installed, and my patch doesn't make it worse?
Oleg.
next prev parent reply other threads:[~2026-10-30 23:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 15:43 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 [this message]
2026-10-30 23:54 ` Joe Perches
2026-10-31 0:11 ` Oleg Nesterov
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=auUps7Hy7W0SqWw3@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 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®