From: Jakub Kicinski <kuba@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.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 17:27:58 -0700 [thread overview]
Message-ID: <20230726172758.3f6462f3@kernel.org> (raw)
In-Reply-To: <20230726-armless-ungodly-a3242f@meerkat>
On Wed, 26 Jul 2023 20:24:06 -0400 Konstantin Ryabitsev wrote:
> On Wed, Jul 26, 2023 at 05:11:23PM -0700, Jakub Kicinski wrote:
> > Hm, hm. I wasn't thrilled by the idea of sending people a notification
> > that "you weren't CCed on this patch, here's a link". But depending on
> > your definition of "hitting the feed" it sounds like we may be able to
> > insert the CC into the actual email before it hits lore? That'd be
> > very cool! At least for the lists already migrated from vger to korg?
>
> No, inserting their addresses into message headers would invalidate DKIM,
> which is not what we want to do. However, the idea is that they would receive
> the actual patches in the same way they would receive them if they were
> subscribed to a mailing list.
Ugh, right :S
> 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.
next prev parent reply other threads:[~2023-07-27 0:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 15:15 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 [this message]
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=20230726172758.3f6462f3@kernel.org \
--to=kuba@kernel.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=konstantin@linuxfoundation.org \
--cc=krzysztof.kozlowski@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox