From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stefan@marxist.se, emacs-devel@gnu.org
Subject: Re: Emacs pretest 28.0.91 is out
Date: Wed, 12 Jan 2022 09:28:43 +0100 [thread overview]
Message-ID: <87pmox4atg.fsf@gmail.com> (raw)
In-Reply-To: <83iluq6rss.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 11 Jan 2022 20:38:59 +0200")
>>>>> On Tue, 11 Jan 2022 20:38:59 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> From: Robert Pluim <rpluim@gmail.com>
>> Cc: stefan@marxist.se, emacs-devel@gnu.org
>> Date: Tue, 11 Jan 2022 18:45:09 +0100
>>
Eli> If the fixes are simple enough, we could backport them The test suite
Eli> is not really critical for the success of a release, so we can install
Eli> changes in it which we won't in the "main" code.
>>
>> It would basically be the attached, although Iʼll note that the tests
>> theyʼre using to determine if gcc is clang are different.
Eli> I don't object to backporting those.
Done. What about trapping errors from ispell-valid-dictionary-list in
lisp/so-long-tests/spelling-tests.el? I mean, my hunspell installation
is borked, because brew on macOS doesnʼt install any dictionaries by
default, so itʼs not entirely a test suite issue.
Robert
--
next prev parent reply other threads:[~2022-01-12 8:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADwFkmm1-qstLz2B80_wEZH3FjvAfdg-+2W1eMQg6J-6_wC7mw__6229.00487376086$1641854896$gmane$org@mail.gmail.com>
2022-01-11 11:43 ` Emacs pretest 28.0.91 is out Robert Pluim
2022-01-11 12:50 ` Michael Albinus
2022-01-11 13:25 ` Robert Pluim
2022-01-11 14:14 ` Robert Pluim
2022-01-11 17:06 ` Eli Zaretskii
2022-01-11 17:45 ` Robert Pluim
2022-01-11 18:38 ` Eli Zaretskii
2022-01-12 8:28 ` Robert Pluim [this message]
2022-01-12 13:35 ` Eli Zaretskii
2022-01-12 14:15 ` Robert Pluim
2022-01-12 14:22 ` Eli Zaretskii
2022-01-12 14:33 ` Robert Pluim
2022-01-12 15:03 ` Eli Zaretskii
2022-01-12 11:24 ` Michael Albinus
2022-01-12 12:59 ` Robert Pluim
2022-01-12 13:11 ` Michael Albinus
2022-01-10 22:39 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=87pmox4atg.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).