From: Eli Zaretskii <eliz@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: mirai@makinata.eu, 66330@debbugs.gnu.org
Subject: bug#66330: 28.2; Gnus wide reply (S W) changes Subject header when used from Debbugs thread
Date: Wed, 04 Oct 2023 10:29:43 +0300 [thread overview]
Message-ID: <83mswy6e1k.fsf@gnu.org> (raw)
In-Reply-To: <87v8bn6xn1.fsf@gmail.com> (message from Maxim Cournoyer on Tue, 03 Oct 2023 20:26:26 -0400)
> Cc: Bruno Victal <mirai@makinata.eu>
> From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
> Date: Tue, 03 Oct 2023 20:26:26 -0400
>
> When attempting to reply from an Emacs Debbugs thread specific email,
> the Subject line gets set to the subject of the first email in the
> thread rather than to that of the specific email I'm replying to, which
> looses context.
The Subject lines of emails pertaining to a discussion of a bug should
never be changed. So I see no problem here, unless I'm missing
something.
Michael, am I wrong?
> 1. M-x debbugs-gnu-bugs 65479
>
> 2. Press 'a' to load the bug despite the lack of SSL certificates.
>
> 3. Navigate to the message titled:
> [bug#65479] [PATCH core-updates 02/61] gnu: Add docbook-xml-5.
>
> 4. Press S W to send a wide reply.
>
> 5. Observe that the Subject header in the email response being edited
> has been changed to "Re: bug#65479: [PATCH core-updates 00/61] The
> Draining of the XML & DocBook Swamp.", that is, the original subject of
> the "bug" (its first message).
This is a bad Subject line to begin with, from where I stand: it
should not include the patch series numbers, and it should not assume
there will be additional messages with different series numbers.
The Subject lines in a bug/issue discussion should describe the
bug/issue, not the patches sent to fix the issue.
next prev parent reply other threads:[~2023-10-04 7:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 0:26 bug#66330: 28.2; Gnus wide reply (S W) changes Subject header when used from Debbugs thread Maxim Cournoyer
2023-10-04 7:29 ` Eli Zaretskii [this message]
2023-10-04 7:53 ` Michael Albinus
2023-10-04 8:31 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-04 8:45 ` Eli Zaretskii
2023-10-04 9:11 ` Michael Albinus
2023-10-04 16:33 ` Eli Zaretskii
2023-10-06 6:48 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-04 9:29 ` Michael Albinus
2023-10-04 14:58 ` Maxim Cournoyer
2023-10-04 12:10 ` Michael Albinus
2023-10-04 20:12 ` Maxim Cournoyer
2023-10-05 7:53 ` Michael Albinus
2023-10-05 13:00 ` 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=83mswy6e1k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66330@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=mirai@makinata.eu \
/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.