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 12:25:15 +0300 [thread overview]
Message-ID: <8335ela8sk.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmkg-ZpSbj9vswvKiSU2pB5R1GH93umo5Y4rFWrH_irYfA@mail.gmail.com> (message from Stefan Kangas on Thu, 28 Jul 2022 11:14:57 +0200)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Thu, 28 Jul 2022 11:14:57 +0200
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, Emacs developers <emacs-devel@gnu.org>, Po Lu <luangruo@yahoo.com>
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I think you are taking this too seriously. A known failure on master
> > shouldn't hold off the merge, IMO. Can't you ignore the test failure?
>
> Sure, it's a bit more work is all. It's not the end of the world, but
> I'd prefer if we could avoid breaking the test suite on master
> instead.
But you aren't breaking the test suite, it's already broken.
The part of automerge that runs the test suite is meant to ensure that
the merge doesn't introduce new regressions. This is not that case.
next prev parent reply other threads:[~2022-07-28 9:25 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
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 [this message]
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=8335ela8sk.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).