From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: "Augusto Stoffel" <arstoffel@gmail.com>,
57877@debbugs.gnu.org, "Daniel Martín" <mardani29@yahoo.es>
Subject: bug#57877: [PATCH] Add empty X-Debbugs-Cc header to bug report template
Date: Sat, 24 Aug 2024 13:13:38 +0200 [thread overview]
Message-ID: <878qwmfa1p.fsf@gmx.de> (raw)
In-Reply-To: <CADwFkmkjBfhBbEmsMqc9OtDbpKH9btMscUkjrWDcKxxCO6XnSw@mail.gmail.com> (Stefan Kangas's message of "Sat, 17 Sep 2022 14:04:12 -0400")
Stefan Kangas <stefankangas@gmail.com> writes:
> Daniel Martín via "Bug reports for GNU Emacs, the Swiss army knife of
> text editors" <bug-gnu-emacs@gnu.org> writes:
>
>> I think this change may confuse some users because there will be a blank
>> X-Debbugs-Cc header when reporting a bug (they'll ask themselves "what
>> should I put here?, what does this do?"). I think we should update the
>> bug template to explain when to fill that special mail header, at least.
>
> I think we should just make `message-goto-cc' command use
> "X-Debbugs-CC" in both `report-emacs-bug' and `submit-emacs-patch'.
Apparently, the requested header is added in `report-emacs-bug' by commit
040cba5d3332. Shouldn't we do the same for `submit-emacs-patch', and
close the bug?
Best regards, Michael.
next prev parent reply other threads:[~2024-08-24 11:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 8:45 bug#57877: [PATCH] Add empty X-Debbugs-Cc header to bug report template Augusto Stoffel
2022-09-17 9:31 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-17 11:45 ` Augusto Stoffel
2022-09-17 18:04 ` Stefan Kangas
2022-09-18 7:39 ` Michael Albinus
2022-09-18 8:16 ` Stefan Kangas
2022-09-18 10:57 ` Lars Ingebrigtsen
2024-08-24 11:13 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-09-14 13:32 ` Stefan Kangas
2024-09-27 7:36 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=878qwmfa1p.fsf@gmx.de \
--to=bug-gnu-emacs@gnu.org \
--cc=57877@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=mardani29@yahoo.es \
--cc=michael.albinus@gmx.de \
--cc=stefankangas@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/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.