From: Augusto Stoffel <arstoffel@gmail.com>
To: "Daniel Martín" <mardani29@yahoo.es>
Cc: 57877@debbugs.gnu.org
Subject: bug#57877: [PATCH] Add empty X-Debbugs-Cc header to bug report template
Date: Sat, 17 Sep 2022 13:45:50 +0200 [thread overview]
Message-ID: <87illmb4wh.fsf@gmail.com> (raw)
In-Reply-To: <m14jx6tki5.fsf@yahoo.es> ("Daniel Martín"'s message of "Sat, 17 Sep 2022 11:31:30 +0200")
On Sat, 17 Sep 2022 at 11:31, Daniel Martín wrote:
> Augusto Stoffel <arstoffel@gmail.com> writes:
>
>> Tags: patch
>>
>> I can never remember what that funny CC header was when I need it, how
>> about adding an empty X-Debbugs-Cc to the bug report and patch message
>> templates?
>>
>> An alternative would be to add a reminder and explanation about it to
>> that portion of text that gets deleted (“This bug report will be
>> sent...”).
>>
>
> 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.
>
> But, if the problem is not general enough, we may simply expose a custom
> variable so that users can provide custom headers in bug reports. With
> that approach, sending bug reports to Emacs by default remains as simple
> as before, while experienced bug reporters can still provide the mail
> header in their customizations, if they want to.
>
> Opinions?
That makes sense. From my perspective either (or both) alternatives you
propose are good.
next prev parent reply other threads:[~2022-09-17 11:45 UTC|newest]
Thread overview: 7+ 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 [this message]
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
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87illmb4wh.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=57877@debbugs.gnu.org \
--cc=mardani29@yahoo.es \
/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/emacs.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).