From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: scratch/igc: Avoid MPS being interrupted by signals Date: Wed, 08 Jan 2025 15:27:53 +0200 Message-ID: <86zfk1306e.fsf@gnu.org> References: <87ldvlg17a.fsf@protonmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36242"; mail-complaints-to="usenet@ciao.gmane.io" Cc: pipcet@protonmail.com, emacs-devel@gnu.org To: Gerd =?utf-8?Q?M=C3=B6llmann?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jan 08 14:29:28 2025 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tVW7k-0009IM-3u for ged-emacs-devel@m.gmane-mx.org; Wed, 08 Jan 2025 14:29:28 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tVW6t-0006rA-UC; Wed, 08 Jan 2025 08:28:36 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tVW6s-0006qK-3W for emacs-devel@gnu.org; Wed, 08 Jan 2025 08:28:34 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tVW6r-0002QK-RI; Wed, 08 Jan 2025 08:28:33 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=XuQnwGiiqtJ2yl6JhIbNR6SIzRvmyu9VFpR3jmUdrFc=; b=RE+INqfx/4C4+sIGQLxn FR/uPZUxVdFGKSHVm/fKOKIVDcf6TlJH4jtw7gnAB5GLRKedMGBBVY6i9DPoX/Q1RkfHx0qd0TOTb TxxkBEo2rDc23K18Us8vamoSeW9z8kHC4LfW/SJZ+ItcqZ+kk2f/DNQCNRvuMEVUr5M60pUmtXUyd UAOF6Ta4mow5TyLJuXnXA0k3/Ceo188q5CQ50TCWR2+OfNYIEksKmXTaVlWJw0RvDJqgzoiWw2tra /wp4KMK92BVv2p3diOmxvqtX0LI7b5ihpguBlQ0mkTml6Aq3w6yjJVgGI6Gzx2Un56RZj5emYjhqU cZtxTUcJrjVmQg==; In-Reply-To: (message from Gerd =?utf-8?Q?M?= =?utf-8?Q?=C3=B6llmann?= on Wed, 08 Jan 2025 10:34:14 +0100) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:327789 Archived-At: > From: Gerd Möllmann > Cc: Emacs Devel > Date: Wed, 08 Jan 2025 10:34:14 +0100 > > Pip Cet 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.