GNU bug report logs -
#57877
[PATCH] Add empty X-Debbugs-Cc header to bug report template
Previous Next
Reported by: Augusto Stoffel <arstoffel <at> gmail.com>
Date: Sat, 17 Sep 2022 08:47:02 UTC
Severity: wishlist
Fixed in version 31.1
Done: Michael Albinus <michael.albinus <at> gmx.de>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 57877 in the body.
You can then email your comments to 57877 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57877
; Package
emacs
.
(Sat, 17 Sep 2022 08:47:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Augusto Stoffel <arstoffel <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sat, 17 Sep 2022 08:47:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
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...”).
In GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.34, cairo version 1.17.6) of 2022-09-14 built on ars3
Repository revision: a9941269683fe50673d0aa81feefb7a9d3d8a6b9
Repository branch: HEAD
System Description: Fedora Linux 36 (Workstation Edition)
Configured using:
'configure --with-pgtk'
[0001-Add-empty-X-Debbugs-Cc-header-to-bug-report-template.patch (text/patch, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57877
; Package
emacs
.
(Sat, 17 Sep 2022 09:32:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 57877 <at> debbugs.gnu.org (full text, mbox):
Augusto Stoffel <arstoffel <at> 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?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57877
; Package
emacs
.
(Sat, 17 Sep 2022 11:46:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 57877 <at> debbugs.gnu.org (full text, mbox):
On Sat, 17 Sep 2022 at 11:31, Daniel Martín wrote:
> Augusto Stoffel <arstoffel <at> 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.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57877
; Package
emacs
.
(Sat, 17 Sep 2022 18:05:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 57877 <at> debbugs.gnu.org (full text, mbox):
Daniel Martín via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs <at> 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'.
For extra points, make it do the same if "bug-gnu-emacs <at> gnu.org" (and
some other well-known debbugs lists, customizable) is already in the
"To:" header.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57877
; Package
emacs
.
(Sun, 18 Sep 2022 07:40:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 57877 <at> debbugs.gnu.org (full text, mbox):
Stefan Kangas <stefankangas <at> gmail.com> writes:
Hi,
> For extra points, make it do the same if "bug-gnu-emacs <at> gnu.org" (and
> some other well-known debbugs lists, customizable) is already in the
> "To:" header.
<https://debbugs.gnu.org/Packages.html> lists the currently hosted
projects on debbugs.gnu.org. The "Bug mailing list" column contains a
link to the project specific bug mailing lists, email addresses for bug
submissions could be extracted from there.
Yes, it would be some work to earn the bonus points :-)
Best regards, Michael.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57877
; Package
emacs
.
(Sun, 18 Sep 2022 08:17:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 57877 <at> debbugs.gnu.org (full text, mbox):
Michael Albinus <michael.albinus <at> gmx.de> writes:
> <https://debbugs.gnu.org/Packages.html> lists the currently hosted
> projects on debbugs.gnu.org.
And then the Debian bug tracker itself, of course.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57877
; Package
emacs
.
(Sun, 18 Sep 2022 10:58:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 57877 <at> debbugs.gnu.org (full text, mbox):
Stefan Kangas <stefankangas <at> gmail.com> writes:
> I think we should just make `message-goto-cc' command use
> "X-Debbugs-CC" in both `report-emacs-bug' and `submit-emacs-patch'.
Or just add new commands to insert debbugs headers when reporting a
bug -- I think that's simpler.
Removed tag(s) patch.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Sun, 18 Sep 2022 10:58:02 GMT)
Full text and
rfc822 format available.
Severity set to 'wishlist' from 'normal'
Request was from
Stefan Kangas <stefankangas <at> gmail.com>
to
control <at> debbugs.gnu.org
.
(Thu, 13 Oct 2022 13:49:07 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57877
; Package
emacs
.
(Sat, 24 Aug 2024 11:15:02 GMT)
Full text and
rfc822 format available.
Message #30 received at 57877 <at> debbugs.gnu.org (full text, mbox):
Stefan Kangas <stefankangas <at> gmail.com> writes:
> Daniel Martín via "Bug reports for GNU Emacs, the Swiss army knife of
> text editors" <bug-gnu-emacs <at> 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.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57877
; Package
emacs
.
(Sat, 14 Sep 2024 13:34:02 GMT)
Full text and
rfc822 format available.
Message #33 received at 57877 <at> debbugs.gnu.org (full text, mbox):
Michael Albinus <michael.albinus <at> gmx.de> writes:
> Stefan Kangas <stefankangas <at> gmail.com> writes:
>
>> Daniel Martín via "Bug reports for GNU Emacs, the Swiss army knife of
>> text editors" <bug-gnu-emacs <at> 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?
Makes sense to me.
Reply sent
to
Michael Albinus <michael.albinus <at> gmx.de>
:
You have taken responsibility.
(Fri, 27 Sep 2024 07:37:04 GMT)
Full text and
rfc822 format available.
Notification sent
to
Augusto Stoffel <arstoffel <at> gmail.com>
:
bug acknowledged by developer.
(Fri, 27 Sep 2024 07:37:04 GMT)
Full text and
rfc822 format available.
Message #38 received at 57877-done <at> debbugs.gnu.org (full text, mbox):
Version: 31.1
Stefan Kangas <stefankangas <at> gmail.com> writes:
> Michael Albinus <michael.albinus <at> gmx.de> writes:
>
>> Stefan Kangas <stefankangas <at> gmail.com> writes:
>>
>>> Daniel Martín via "Bug reports for GNU Emacs, the Swiss army knife of
>>> text editors" <bug-gnu-emacs <at> 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?
>
> Makes sense to me.
Done, pushed to master. Closing the bug.
Best regards, Michael.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Fri, 25 Oct 2024 11:24:13 GMT)
Full text and
rfc822 format available.
This bug report was last modified 219 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.