From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rgm@gnu.org, stefan@marxist.se, contovob@tcd.ie,
p.stephani2@gmail.com, Stefan Monnier <monnier@iro.umontreal.ca>,
46722@debbugs.gnu.org, dick.r.chiang@gmail.com
Subject: bug#46722: test-map-into fails
Date: Thu, 20 Jan 2022 13:49:55 +0100 [thread overview]
Message-ID: <87bl061si4.fsf@gnus.org> (raw)
In-Reply-To: <83tue5yox6.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 15 Jan 2022 17:55:01 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> It's already the second time I say it, so I promise it's the last time
>> I insist here. I can live with either choice, but I'm sure Emacs-28 will
>> be better off with the patch than without.
>
> My opinion is up-thread, so I guess it's up to Lars now.
I agree with Eli.
And since this is fixed in Emacs 29 (and the tests marked in Emacs 28),
I'm therefore closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-01-20 12:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 16:22 bug#46722: test-map-into fails Glenn Morris
2021-02-23 16:33 ` Basil L. Contovounesios
2021-02-23 17:06 ` Glenn Morris
2021-02-23 17:30 ` Stefan Monnier
2021-02-23 20:58 ` Basil L. Contovounesios
2021-02-23 22:50 ` Basil L. Contovounesios
2021-04-04 16:05 ` Glenn Morris
2021-11-17 8:47 ` Stefan Kangas
2021-11-29 18:20 ` Glenn Morris
2021-11-29 18:26 ` Lars Ingebrigtsen
2021-11-29 18:40 ` Glenn Morris
2022-01-04 21:56 ` dick
2022-01-05 14:01 ` dick
2022-01-05 16:31 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-05 17:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-05 18:07 ` Eli Zaretskii
2022-01-05 18:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-13 19:23 ` Philipp Stephani
2022-01-13 20:40 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-13 20:45 ` Philipp Stephani
2022-01-14 7:40 ` Lars Ingebrigtsen
2022-01-14 12:02 ` Philipp Stephani
2022-01-15 8:01 ` Lars Ingebrigtsen
2022-01-15 11:47 ` Philipp Stephani
2022-01-15 15:16 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-15 15:55 ` Eli Zaretskii
2022-01-20 12:49 ` Lars Ingebrigtsen [this message]
2022-01-05 15:17 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-05 16:04 ` dick
2022-01-05 16:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-05 18:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-05 18:59 ` dick
2022-01-05 19:17 ` Stefan Monnier 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=87bl061si4.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=46722@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=dick.r.chiang@gmail.com \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=p.stephani2@gmail.com \
--cc=rgm@gnu.org \
--cc=stefan@marxist.se \
/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).