[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230728-egotism-icing-3d0bd0@meerkat>
Date: Fri, 28 Jul 2023 16:29:13 -0400
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Andrew Lunn <andrew@...n.ch>
Cc: Jakub Kicinski <kuba@...nel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>, 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, mario.limonciello@....com
Subject: Re: [PATCH v2] scripts: get_maintainer: steer people away from using
file paths
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.
-K
Powered by blists - more mailing lists