From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
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 20:33:16 -0400 [thread overview]
Message-ID: <20230726-yeah-acrobat-ba1acf@meerkat> (raw)
In-Reply-To: <20230726172758.3f6462f3@kernel.org>
On Wed, Jul 26, 2023 at 05:27:58PM -0700, Jakub Kicinski wrote:
> > Think as if instead of being Cc'd on patches, they got Bcc'd on them.
>
> I was being crafty 'cause if the CC is present in the lore archive
> our patchwork check would see it :]
> But cant just trust the automation and kill the check, then.
If we can get it working reliably and to everyone's satisfaction, then I think
the need for this check goes away. The submitter can then just worry about
getting *everything else* right about the patch and not worry about who to add
into Cc's.
-K
next prev parent reply other threads:[~2023-07-27 0:33 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
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 [this message]
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=20230726-yeah-acrobat-ba1acf@meerkat \
--to=konstantin@linuxfoundation.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=torvalds@linux-foundation.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.