From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: 63378@debbugs.gnu.org
Cc: rekado@elephly.net, arunisaac@systemreboot.net
Subject: bug#63378: A single X-Debbugs-CC header must be used
Date: Tue, 09 May 2023 09:33:07 -0400 [thread overview]
Message-ID: <87y1lxsk8c.fsf_-_@gmail.com> (raw)
In-Reply-To: <3e14e27ad26ce9dee230733c7e77935b5f43599d.1683570582.git.maxim.cournoyer@gmail.com> (Maxim Cournoyer's message of "Mon, 8 May 2023 14:29:42 -0400")
Hello,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> Fixes <https://issues.guix.gnu.org/63378>.
>
> * etc/teams.scm.in (cc): Adjust format pattern.
> (team->members, member->string): New procedures.
> (list-members): Refactor in terms of the above procedures.
> (main): Adjust the output of the 'cc-members-header-cmd' and
> 'cc-mentors-header-cmd' actions.
Paul from Debian has posted a merge request to the upstream Debbugs [0]
that would make it possible to use multiple X-Debbugs-CC.
Now, I don't think the GNU Debbugs instance is kept up-to-date with
Debbugs upstream, having its own set of changes, so I think the patch
here should still be applied in the meantime.
[0] https://salsa.debian.org/debbugs-team/debbugs/-/merge_requests/18/diffs
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-05-09 13:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 17:17 bug#63378: A single X-Debbugs-CC header must be used Maxim Cournoyer
2023-05-08 18:29 ` bug#63378: [PATCH] teams: Fix script to produce a single X-Debbugs-Cc header Maxim Cournoyer
2023-05-09 13:33 ` Maxim Cournoyer [this message]
2023-05-09 23:43 ` bug#63378: A single X-Debbugs-CC header must be used Arun Isaac
2023-05-10 1:15 ` Maxim Cournoyer
2023-05-09 23:55 ` bug#63378: [PATCH] teams: Fix script to produce a single X-Debbugs-Cc header Arun Isaac
2023-05-10 16:15 ` Maxim Cournoyer
2023-05-11 11:13 ` Arun Isaac
2023-05-11 13:18 ` Maxim Cournoyer
2023-05-11 23:59 ` Arun Isaac
2023-05-10 2:55 ` bug#63378: [PATCH v2] " 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y1lxsk8c.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=63378@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
--cc=rekado@elephly.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).