From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 64151@debbugs.gnu.org, Christopher Baines <mail@cbaines.net>,
Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: [bug#64151] [PATCH] etc: Stop making sendemail behave strangely.
Date: Mon, 10 Jul 2023 23:21:20 +0200 [thread overview]
Message-ID: <871qhf8nu7.fsf@gnu.org> (raw)
In-Reply-To: <878rboxujs.fsf@gmail.com> (Maxim Cournoyer's message of "Mon, 10 Jul 2023 00:24:55 -0400")
Hello!
It just occurred to me that we might have a reasonable tradeoff at hand:
instead of adding Cc: or X-Debbugs-Cc: headers, we could add, say,
X-Guix-Team: headers. That way, team members would be free to filter
incoming messages however they want.
How does that sound?
Of course if team members don’t pay attention to that header, we’re back
to square one, but hopefully that won’t be the case.
Ludo’.
next prev parent reply other threads:[~2023-07-10 21:22 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 [this message]
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 ` bug#64151: " Maxim Cournoyer
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=871qhf8nu7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=64151@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=mail@cbaines.net \
--cc=maxim.cournoyer@gmail.com \
/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.