[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <63361a8f-ffa5-50e7-97d6-297d8e8b059f@amd.com>
Date: Wed, 26 Jul 2023 13:45:38 -0500
From: "Limonciello, Mario" <mario.limonciello@....com>
To: Linus Torvalds <torvalds@...ux-foundation.org>,
Jakub Kicinski <kuba@...nel.org>
Cc: Joe Perches <joe@...ches.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, geert@...ux-m68k.org,
gregkh@...uxfoundation.org, netdev@...r.kernel.org, workflows@...r.kernel.org
Subject: Re: [PATCH v2] scripts: get_maintainer: steer people away from using
file paths
On 7/26/2023 1:29 PM, Linus Torvalds wrote:
> On Wed, 26 Jul 2023 at 11:20, Jakub Kicinski <kuba@...nel.org> wrote:
>>
>> You are special,
>
> So my mother tells me.
>
>> you presumably use it to find who to report
>> regressions to, and who to pull into conversations.
>
> Yes. So what happens is that I get cc'd on bug reports for various
> issues, and particularly for oops reports I basically have a function
> name to grep for (maybe a pathname if it went through the full
> decoding).
>
> I'm NOT interested in having to either remember all people off-hand,
> or going through the MAINTAINERS file by hand.
>
>> This tool is primarily used by _developers_ to find _maintainers_.
>
> Well, maybe.
>
> But even if that is true, I don't see why you hate the pathname thing
> even for that case. I bet developers use it for that exact same
> reason, ie they are modifying a file, and they go "I want to know who
> the maintainer for this file is".
>
> I do not understand why you think a patch is somehow magically more
> important or relevant than a filename.
>
> Linus
If the goal is to get people who are involved with a file, how about
some variation of:
git log --pretty=format:%ae $PATH | sort | uniq
Granted this is going to be overkill, for example I can see on
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c that it would email 198 people.
Powered by blists - more mailing lists