All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Joe Perches <joe@perches.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	 geert@linux-m68k.org, gregkh@linuxfoundation.org,
	netdev@vger.kernel.org,  workflows@vger.kernel.org,
	mario.limonciello@amd.com
Subject: Re: [PATCH v2] scripts: get_maintainer: steer people away from using file paths
Date: Wed, 26 Jul 2023 15:15:41 -0700	[thread overview]
Message-ID: <CAHk-=wjrk1O+a74xKbKMNshZc9dKByWbyXvW+Wre=DQwPjTKGA@mail.gmail.com> (raw)
In-Reply-To: <20230726145721.52a20cb7@kernel.org>

On Wed, 26 Jul 2023 at 14:57, Jakub Kicinski <kuba@kernel.org> wrote:
>
> Lots of those will be false positives, and also I do not want
> to sign up to maintain a bot which actively bothers people.

I don't really see the difference between creating a bot that
"actively bothers people" and asking _people_ to run a script and then
re-send the patch to actively bother the exact same people.

They'd get bothered either way.

At least with the bot, they can opt out of the automation.

> Sidebar, but IMO we should work on lore to create a way to *subscribe*
> to patches based on paths without running any local agents.

I already contacted Konstantin to see how hard it would be to change
patchwork-bot scripting, and he's trawling this thread.

Maybe he will just go "the code already does all the patch detection
and looks up pathnames in them anyway, and we already maintain a list
of people who do not want to be bothered, it would be easy to add the
'please bother me for these paths' script too".

             Linus

  parent reply	other threads:[~2023-07-26 22:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 15:15 [PATCH v2] scripts: get_maintainer: steer people away from using file paths Jakub Kicinski
2023-07-26 15:20 ` Mario Limonciello
2023-07-26 15:43 ` Joe Perches
2023-07-26 16:23   ` Jakub Kicinski
2023-07-26 16:45     ` Linus Torvalds
2023-07-26 16:51       ` Joe Perches
2023-07-26 18:20       ` Jakub Kicinski
2023-07-26 18:29         ` Linus Torvalds
2023-07-26 18:45           ` Limonciello, Mario
2023-07-26 18:48             ` Linus Torvalds
2023-07-26 18:48           ` Jakub Kicinski
2023-07-26 18:59             ` Linus Torvalds
2023-07-26 19:05               ` Linus Torvalds
2023-07-26 19:37                 ` Linus Torvalds
2023-07-26 20:03                   ` Jakub Kicinski
2023-07-26 20:13                     ` Linus Torvalds
2023-07-26 20:36                       ` Jakub Kicinski
2023-07-26 21:07                         ` Linus Torvalds
2023-07-26 21:57                           ` Jakub Kicinski
2023-07-26 22:02                             ` Linus Torvalds
2023-07-26 22:15                             ` Linus Torvalds [this message]
2023-07-26 23:47                             ` Konstantin Ryabitsev
2023-07-27  0:11                               ` Jakub Kicinski
2023-07-27  0:24                                 ` Konstantin Ryabitsev
2023-07-27  0:27                                   ` Jakub Kicinski
2023-07-27  0:33                                     ` Konstantin Ryabitsev
2023-07-27  1:07                                       ` Joe Perches
2023-07-27 11:00                                   ` Andrew Lunn
2023-07-28 20:29                                     ` Konstantin Ryabitsev
2023-07-28 20:38                                       ` Jakub Kicinski
2023-07-28 20:50                                         ` Konstantin Ryabitsev
2023-07-29  0:22                                       ` Joe Perches

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='CAHk-=wjrk1O+a74xKbKMNshZc9dKByWbyXvW+Wre=DQwPjTKGA@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=kuba@kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=netdev@vger.kernel.org \
    --cc=workflows@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 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.