From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>
Cc: mirai@makinata.eu, michael.albinus@gmx.de, 66330@debbugs.gnu.org,
maxim.cournoyer@gmail.com
Subject: bug#66330: 28.2; Gnus wide reply (S W) changes Subject header when used from Debbugs thread
Date: Wed, 04 Oct 2023 11:45:15 +0300 [thread overview]
Message-ID: <83fs2q6ajo.fsf@gnu.org> (raw)
In-Reply-To: <87ttr6zt38.fsf@thaodan.de> (message from Björn Bidar on Wed, 04 Oct 2023 11:31:55 +0300)
> From: Björn Bidar <bjorn.bidar@thaodan.de>
> Cc: Eli Zaretskii <eliz@gnu.org>, mirai@makinata.eu,
> 66330@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
> Date: Wed, 04 Oct 2023 11:31:55 +0300
>
> Michael Albinus <michael.albinus@gmx.de> writes:
>
> >> The Subject lines in a bug/issue discussion should describe the
> >> bug/issue, not the patches sent to fix the issue.
> >
> > 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!).
>
> The `[PATCH patch-number/patch-count] Subject` subject format is also the
> generate format for Git patch-series. The Guix subject format is a
> variant of this.
>
> The subject changing could be an issue outside of Gnus. E.g when
> responding to a patch in git patch series outside of Guix.
>
> However I think it is a general issue that mail clients append Re: or
> some localized variation of it.
Re: and its localized variants are not a problem: all Emacs MUAs
support that and know how to ignore them for threading purposes.
next prev parent reply other threads:[~2023-10-04 8:45 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 [this message]
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
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=83fs2q6ajo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66330@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=maxim.cournoyer@gmail.com \
--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).