From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Pip Cet <pipcet@protonmail.com>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: scratch/igc: Avoid MPS being interrupted by signals
Date: Wed, 08 Jan 2025 10:34:14 +0100 [thread overview]
Message-ID: <m2v7upbqeh.fsf@gmail.com> (raw)
In-Reply-To: <87ldvlg17a.fsf@protonmail.com> (Pip Cet's message of "Wed, 08 Jan 2025 08:27:24 +0000")
Pip Cet <pipcet@protonmail.com> writes:
> I don't know what you decided wrt scratch/igc and Eli.
I just looked at the situation. The branch was stuck, the discussions
were stuck. Everyone is entitled to have his worries of course, but I'm
poking about in the fog why Eli is worried, and I'm obviously unable to
explain things well enough or induce enough trust to make this work.
That's why I think it's currently not wise pursuing a merge, at least
with the persons involved so far. It's too draining and in the end only
leads to ill feelings.
Whatever.
Someone from the outside is needed to solve this. Maybe Daniel can
explain things better. Or maybe one should ask Stefan Monnier to get
involved, or the other maintainers, I don't know.
Not my problem, TBH. Being reckless again :-).
next prev parent reply other threads:[~2025-01-08 9:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 4:07 scratch/igc: Avoid MPS being interrupted by signals Gerd Möllmann
2025-01-08 8:27 ` Pip Cet via Emacs development discussions.
2025-01-08 9:34 ` Gerd Möllmann [this message]
2025-01-08 12:11 ` Pip Cet via Emacs development discussions.
2025-01-08 13:27 ` Eli Zaretskii
2025-01-08 14:08 ` Gerd Möllmann
2025-01-08 14:18 ` Eli Zaretskii
2025-01-08 14:46 ` Gerd Möllmann
2025-01-08 15:42 ` Eli Zaretskii
2025-01-08 17:30 ` Gerd Möllmann
2025-01-08 18:44 ` Eli Zaretskii
2025-01-08 8:32 ` Pip Cet via Emacs development discussions.
2025-01-08 9:35 ` Gerd Möllmann
2025-01-08 12:07 ` Pip Cet via Emacs development discussions.
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=m2v7upbqeh.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=pipcet@protonmail.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).