unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Eli Zaretskii <eliz@gnu.org>, 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:58:04 -0400	[thread overview]
Message-ID: <877co2305f.fsf@gmail.com> (raw)
In-Reply-To: <87sf6qhli9.fsf@gmx.de> (Michael Albinus's message of "Wed, 04 Oct 2023 09:53:02 +0200")

Hello,

Michael Albinus <michael.albinus@gmx.de> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
> Hi Eli,
>
>>> 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?
>
> Well, we haven't documented such a rule. But based on my experience I
> would agree. There's often a message in the bug-gnu-emacs@gnu.org ML
> with the subject "bug#xxxxx: Patch" or alike, which doesn't help. I'm
> too old to remember all the bug numbers and their related topic, and I
> read only messages in that ML with topics I'm interested in.
>
>>> 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.

When working on bugs, I agree this behavior makes sense, where the
original bug title should be kept around.  I'm fine with that behavior
for the 'bug-guix' tracker, which tracks bugs.  Where I'd like to be
able to customize/change that behavior is when working with *patches*
posted to guix-patches, which is also hosted on Debbugs.

These patches typically get sent via 'git send-email' and include in
their subject the patch number, e.g. [PATCH v2 12/62].  I want this
preserved when reviewing the patch, so that participant knows what was
reviewed.

> D'accord. But I guess the subject line quoted here is created by a tool
> of the guix-patches toolchain. So first we shall agree about the rules
> of that toolchain (I'm from Emacs, I won't dictate anything!).
>
> If this is an agreed behavior, we could discuss about a debbugs-gnu user
> option how to handle the subject line of replies, with a different
> default value for guix-patches messages. The global default shouldn't be
> changed.

That sounds good to me.

> Well, we even have already guix specific code, see debbugs-guix.el. I
> would appreciate if somebody from the guix project supports me in
> writing such a patch.

I'm willing to work on it.  It seems you draft a plan in another reply,
which I'll look at now.

-- 
Thanks,
Maxim





  parent reply	other threads:[~2023-10-04 14:58 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
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 [this message]
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

  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=877co2305f.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=66330@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=michael.albinus@gmx.de \
    --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 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).