Gnus development mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: fweimer@redhat.com, larsi@gnus.org, emacs-devel@gnu.org, ding@gnus.org
Subject: Re: master ef14acf: Make nnml handle invalid non-ASCII headers more consistently
Date: Mon, 19 Dec 2022 20:16:51 +0200	[thread overview]
Message-ID: <83r0wvcl7w.fsf@gnu.org> (raw)
In-Reply-To: <87fsdbs1zv.fsf@ericabrahamsen.net> (message from Eric Abrahamsen on Mon, 19 Dec 2022 10:05:24 -0800)

> From: Eric Abrahamsen <eric@ericabrahamsen.net>
> Cc: fweimer@redhat.com,  larsi@gnus.org,  emacs-devel@gnu.org,  ding@gnus.org
> Date: Mon, 19 Dec 2022 10:05:24 -0800
> 
> Sorry, I misunderstood -- I thought this change was introducing a
> difference in the saved files. My mistake for not following along
> closely enough.

No sweat.

> Maybe all this warrants some regression tests in ./test/lisp/mail?

Adding tests is always welcome, TIA.


      reply	other threads:[~2022-12-19 18:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210122180801.14756.84264@vcs0.savannah.gnu.org>
     [not found] ` <20210122180802.F0A1E20A10@vcs0.savannah.gnu.org>
2022-12-16 22:42   ` Florian Weimer
2022-12-17  7:45     ` Eli Zaretskii
2022-12-17 14:57       ` Florian Weimer
2022-12-17 15:52         ` Eli Zaretskii
2022-12-19 13:59           ` Florian Weimer
2022-12-19 17:07             ` Eli Zaretskii
2022-12-19 17:27               ` Florian Weimer
2022-12-19 17:44                 ` Eli Zaretskii
2022-12-19 17:48               ` Eric Abrahamsen
2022-12-19 17:58                 ` Eli Zaretskii
2022-12-19 18:05                   ` Eric Abrahamsen
2022-12-19 18:16                     ` Eli Zaretskii [this message]

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=83r0wvcl7w.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=fweimer@redhat.com \
    --cc=larsi@gnus.org \
    /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.
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 NNTP newsgroup(s).