From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 74658@debbugs.gnu.org, ~@wolfsden.cz
Subject: bug#74658: Remove the Mail-Followup-To header when empty
Date: Tue, 03 Dec 2024 16:18:06 +0200 [thread overview]
Message-ID: <86ttbk26ld.fsf@gnu.org> (raw)
In-Reply-To: <87v7w0euel.fsf@gmail.com> (message from Robert Pluim on Tue, 03 Dec 2024 15:02:58 +0100)
> Cc: 74658@debbugs.gnu.org
> From: Robert Pluim <rpluim@gmail.com>
> Date: Tue, 03 Dec 2024 15:02:58 +0100
>
> >>>>> On Tue, 03 Dec 2024 00:17:10 +0100, Tomas Volf <~@wolfsden.cz> said:
>
> Tomas> Tags: patch
> Tomas> According to the info manual (message)Mailing Lists, the
> Tomas> Mail-Followup-To header should be removed when it is empty:
>
> >> If there is one, it is left alone. (Except if it’s empty; in that
> >> case, the field is removed and is not replaced with an automatically
> >> generated one. This lets you disable MFT generation on a per-message
> >> basis.)
>
> Tomas> While the code attempted to do that, the call to `message-remove-header'
> Tomas> passed wrong arguments. Since the IS-REGEXP argument was not passed,
> Tomas> the HEADER was considered a full header name (if I read the code right)
> Tomas> and therefore failed to match (since the code passed in a regexp instead
> Tomas> of a fixed string).
>
> Tomas> The fix is simple, remove the leading ^ and trailing :.
>
> Yep. I can apply this to master. Maintainers, is adding
> Copyright-paperwork-exempt: yes enough here? Or do we need a copyright
> assignment from Tomas?
"Copyright-paperwork-exempt: yes" is enough.
Thanks.
next prev parent reply other threads:[~2024-12-03 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 23:17 bug#74658: Remove the Mail-Followup-To header when empty Tomas Volf
2024-12-03 14:02 ` Robert Pluim
2024-12-03 14:18 ` Eli Zaretskii [this message]
2024-12-03 15:22 ` Robert Pluim
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=86ttbk26ld.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74658@debbugs.gnu.org \
--cc=rpluim@gmail.com \
--cc=~@wolfsden.cz \
/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.