From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: larsi@gnus.org, emacs-devel@gnu.org, luangruo@yahoo.com
Subject: Re: master bfa951cdfa: Fix invalid current buffer after print-unreadable-function signals
Date: Thu, 28 Jul 2022 11:31:15 +0300 [thread overview]
Message-ID: <83bkt9abak.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnJxVY3fDyP-_rGBdAk=2XSUS69VhC_bpDQ+JXQH=VVqQ@mail.gmail.com> (message from Stefan Kangas on Thu, 28 Jul 2022 01:14:30 -0700)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Thu, 28 Jul 2022 01:14:30 -0700
> Cc: Po Lu <luangruo@yahoo.com>
>
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> > Po Lu via Mailing list for Emacs changes <emacs-diffs@gnu.org> writes:
> >
> >> Fix invalid current buffer after print-unreadable-function signals
> >>
> >> * src/print.c (PRINTPREPARE): Remove `old' and
> >> record_unwind_current_buffer instead.
> >> (PRINTFINISH): Stop restoring `old'. (bug#56773)
> >
> > This apparently leads to:
> >
> > 1 unexpected results:
> > FAILED terpri
> >
> > in print-tests.el.
>
> If there is no quick fix, could we please revert the change?
>
> It's currently stopping me from merging emacs-28 to master.
Why does it prevent a merge?
next prev parent reply other threads:[~2022-07-28 8:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165891496054.3950.2967202128456340980@vcs2.savannah.gnu.org>
[not found] ` <20220727094240.C94FEC0F1E3@vcs2.savannah.gnu.org>
2022-07-27 9:54 ` master bfa951cdfa: Fix invalid current buffer after print-unreadable-function signals Lars Ingebrigtsen
2022-07-28 8:14 ` Stefan Kangas
2022-07-28 8:31 ` Eli Zaretskii [this message]
2022-07-28 8:47 ` Stefan Kangas
2022-07-28 8:59 ` Eli Zaretskii
2022-07-28 9:14 ` Stefan Kangas
2022-07-28 9:25 ` Eli Zaretskii
2022-07-28 9:32 ` Stefan Kangas
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=83bkt9abak.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=stefankangas@gmail.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).