unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Bill Wohler via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cks.emacsbugs-01@cs.toronto.edu, kupfer@rawbw.com, 67360@debbugs.gnu.org
Subject: bug#67360: 29.1; MH-E forwarded email has a mangled default Subject header
Date: Mon, 01 Jan 2024 10:35:13 -0800	[thread overview]
Message-ID: <2129283.1704134113@olgas.newt.com> (raw)
In-Reply-To: <834jfy2nbs.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> wrote:

> > cc: Mike Kupfer <kupfer@rawbw.com>,
> >     Chris Siebenmann <cks.emacsbugs-01@cs.toronto.edu>,
> >     67360@debbugs.gnu.org
> > From: Bill Wohler <wohler@newt.com>
> > Comments: In-reply-to Bill Wohler <wohler@newt.com>
> >    message dated "Sat, 30 Dec 2023 14:05:29 -0800."
> > Date: Sun, 31 Dec 2023 08:44:40 -0800
> > 
> > Eli,
> > 
> > Would you prefer that I apply Mike's patch to emacs-29 or master?
> > 
> > > diff --git a/lisp/mh-e/mh-comp.el b/lisp/mh-e/mh-comp.el
> > > index 92d31bf1826..0d1dcdf626a 100644
> > > --- a/lisp/mh-e/mh-comp.el
> > > +++ b/lisp/mh-e/mh-comp.el
> > > @@ -574,7 +574,7 @@ mh-forward
> > >          (setq orig-subject (mh-get-header-field "Subject:")))
> > >        (let ((forw-subject
> > >               (mh-forwarded-letter-subject orig-from orig-subject)))
> > > -        (mh-insert-fields "Subject:" forw-subject)
> > > +        (mh-modify-header-field "Subject" forw-subject t)
> > >          (goto-char (point-min))
> > >          ;; Set the local value of mh-mail-header-separator according to what is
> > >          ;; present in the buffer...
> 
> If you think it's safe enough for the release branch, emacs-29 is fine
> with me.

I think so, yes. I've pushed the fix and sent what may be my first
message to a *-done email address. It's never too late to start.

-- 
Bill Wohler <wohler@newt.com> aka <Bill.Wohler@nasa.gov>
http://www.newt.com/wohler/, GnuPG ID:610BD9AD





  reply	other threads:[~2024-01-01 18:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22  0:49 bug#67360: 29.1; MH-E forwarded email has a mangled default Subject header Chris Siebenmann
2023-11-22 14:42 ` Eli Zaretskii
2023-11-27  3:49   ` Mike Kupfer
2023-12-30 22:05     ` Bill Wohler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-31 16:44       ` Bill Wohler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-31 19:17         ` Eli Zaretskii
2024-01-01 18:35           ` Bill Wohler via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-01-01 18:33 ` Bill Wohler via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=2129283.1704134113@olgas.newt.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=67360@debbugs.gnu.org \
    --cc=cks.emacsbugs-01@cs.toronto.edu \
    --cc=eliz@gnu.org \
    --cc=kupfer@rawbw.com \
    --cc=wohler@newt.com \
    /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).