From: Joe Perches <joe@perches.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Andrew Lunn <andrew@lunn.ch>
Cc: Jakub Kicinski <kuba@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
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: Fri, 28 Jul 2023 17:22:36 -0700 [thread overview]
Message-ID: <a19576f73036e772225140bb54f433caf0097e4f.camel@perches.com> (raw)
In-Reply-To: <20230728-egotism-icing-3d0bd0@meerkat>
On Fri, 2023-07-28 at 16:29 -0400, Konstantin Ryabitsev wrote:
> On Thu, Jul 27, 2023 at 01:00:15PM +0200, Andrew Lunn wrote:
> > > Think as if instead of being Cc'd on patches, they got Bcc'd on them.
> >
> > And how does reply work? I assume it would only go to those in To: or
> > Cc: ? Is there enough context in the headers in a reply for the system
> > to figure out who to Bcc: the reply to?
>
> I have actually solved a similar problem already as part of a different
> project (bugbot). We associate a set of additional addresses with a thread and
> can send any thread updates to those addresses.
>
> It would require a bit more effort to adapt it so we properly handle bounces,
> but effectively this does what you're asking about -- replies sent to a thread
> will be sent out to all addresses we've associated with that thread (via
> get_maintainer.pl). In a sense, this will create a miniature pseudo-mailing
> list per each thread with its own set of subscribers.
>
> I just need to make sure this doesn't fall over once we are hitting
> LKML-levels of activity.
>
How about whenever a single mailing list like
linux-patches@vger.kernel.org
gets new 0/n without an in-reply-to header and m/n patches with
only the single in-reply-to header of an 0/n patch or simply a
single patch without an in-reply-to header, the cc list is
automatically generated from a tool like get_maintainer and a
From: <sender> line is added if necessary to the message body
and the email forwarded to all cc's and linux-patches is removed
from the email?
I believe that would help solve most correctness of recipient
list issues and then the linux-patches list would not need
further involvement.
prev parent reply other threads:[~2023-07-29 0:22 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
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 [this message]
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=a19576f73036e772225140bb54f433caf0097e4f.camel@perches.com \
--to=joe@perches.com \
--cc=andrew@lunn.ch \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=konstantin@linuxfoundation.org \
--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.