From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: pipcet@protonmail.com, emacs-devel@gnu.org
Subject: Re: scratch/igc: Avoid MPS being interrupted by signals
Date: Wed, 08 Jan 2025 15:27:53 +0200 [thread overview]
Message-ID: <86zfk1306e.fsf@gnu.org> (raw)
In-Reply-To: <m2v7upbqeh.fsf@gmail.com> (message from Gerd Möllmann on Wed, 08 Jan 2025 10:34:14 +0100)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: Emacs Devel <emacs-devel@gnu.org>
> Date: Wed, 08 Jan 2025 10:34:14 +0100
>
> 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 :-).
I don't think I understand why you regard this so pessimistically.
The branch was not stuck, in the sense that no one, certainly not
myself, said commits couldn't be pushed to it. The discussion wasn't
stuck, either, at least from my POV: we just reached the point where I
personally had nothing else useful to say on the subject. Your
explanations (and those of Daniel and others) were helpful, and I
think at least I now understand the issues better. I do still worry
that identifying all the situations where we'd need changes will be a
big and maybe long-term job, but since you-all say that either it
isn't such a big job or there's no way around it, I guess we will
wait-and-see.
Merging is also not an issue: I don't envision the branch landing in
the immediate future, so there's nothing to worry about. I started
the discussion not because I wanted to land the branch right now, but
because I wanted to estimate how much more work is needed.
So I'm afraid I don't see a problem that needs to be solved here,
yours or SE's. To answer Pip's question: there's no decision I know
about that must be made here.
But if someone disagrees, please do speak up. These discussions are
held on emacs-devel precisely for that reason.
next prev parent reply other threads:[~2025-01-08 13:27 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
2025-01-08 12:11 ` Pip Cet via Emacs development discussions.
2025-01-08 13:27 ` Eli Zaretskii [this message]
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=86zfk1306e.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gerd.moellmann@gmail.com \
--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).