From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
64151-done@debbugs.gnu.org,
"Liliana Marie Prikler" <liliana.prikler@gmail.com>
Subject: bug#64151: [PATCH] etc: Stop making sendemail behave strangely.
Date: Wed, 06 Sep 2023 00:49:35 -0400 [thread overview]
Message-ID: <87r0nb9a8w.fsf_-_@gmail.com> (raw)
In-Reply-To: <87ilaitro3.fsf@gmail.com> (Maxim Cournoyer's message of "Mon, 17 Jul 2023 12:43:24 -0400")
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
[...]
>> I'm obviously OK with this when people directly want my input or if I'm
>> already involved in the conversation, but this CC thing has extended
>> that to most/any patch submissions that are detected overlapping with
>> teams I'm in.
>
> Notifying team members of a patch touching their scope is the intended
> behavior of the teams mechanism.
>
>> Maybe this is just because of the email address I used for teams. I've
>> now gone and changed this from mail@cbaines.net to guix@cbaines.net,
>> which comes to the same place, but I'll hopefully be able to use the
>> different address to separate out the emails appropriately.
>
> Of course this behavior now being automated, if you are part of many
> teams, the amount of emails reaching your inbox may be higher than it
> used to be. If the flux is too large for you to process, I'd recommend
> you review and perhaps trim your current teams subscription. One of the
> expected side-effect of notifying team members with etc/teams.scm is
> that it should improve reviews. Keeping our team scopes more focus (and
> encouraging active participation of new team members) should help reduce
> the load in the long run.
Are you OK with closing this issue?
--
Thanks,
Maxim
prev parent reply other threads:[~2023-09-06 4:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 11:49 [bug#64151] [PATCH] etc: Stop making sendemail behave strangely Christopher Baines
2023-06-25 21:06 ` Ludovic Courtès
2023-06-26 14:36 ` Maxim Cournoyer
2023-06-27 19:26 ` Liliana Marie Prikler
2023-06-28 1:14 ` Maxim Cournoyer
2023-06-28 4:30 ` Liliana Marie Prikler
2023-07-01 3:03 ` Maxim Cournoyer
2023-07-01 5:50 ` Liliana Marie Prikler
2023-07-01 16:03 ` Maxim Cournoyer
2023-07-03 9:36 ` Ludovic Courtès
2023-07-06 15:49 ` Maxim Cournoyer
2023-07-08 17:16 ` Liliana Marie Prikler
2023-07-10 4:24 ` Maxim Cournoyer
2023-07-10 21:21 ` Ludovic Courtès
2023-07-11 4:28 ` Liliana Marie Prikler
2023-07-14 13:21 ` Ludovic Courtès
2023-07-14 13:52 ` Liliana Marie Prikler
2023-07-14 14:12 ` Maxim Cournoyer
2023-07-14 13:59 ` Maxim Cournoyer
2023-07-17 13:02 ` Christopher Baines
2023-07-17 16:43 ` Maxim Cournoyer
2023-09-06 4:49 ` Maxim Cournoyer [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=87r0nb9a8w.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=64151-done@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=ludo@gnu.org \
--cc=mail@cbaines.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.