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 16:18:03 +0200 Message-ID: <86v7up2xus.fsf@gnu.org> References: <87ldvlg17a.fsf@protonmail.com> <86zfk1306e.fsf@gnu.org> 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="7566"; 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 15:19:59 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 1tVWub-0001hT-Bz for ged-emacs-devel@m.gmane-mx.org; Wed, 08 Jan 2025 15:19:57 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tVWtw-0000fh-Kn; Wed, 08 Jan 2025 09:19:18 -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 1tVWtU-0000YY-2O for emacs-devel@gnu.org; Wed, 08 Jan 2025 09:18:55 -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 1tVWtS-0007Tc-QM; Wed, 08 Jan 2025 09:18:47 -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=2qu7oRtjOJodYomV9Ti9cM6TCCmBKfa1o5SFVQNpo8M=; b=qITq9gDeIc9BDnL84DGW 5JLMiKZTjthV5HfozzaSMTuMTjKZGSOHrtC9+oP0QxJ5h3uzz2/agkHCc3mDPKfa7Z/5HiVCW12nl G5JrRwkTIbDzsQP8rAxGZ4YStZVPY03avJHJnpHbkL5wtcmkXX6iy/z2jTutbUq7Bdxm67K5I/AoG 1hX9OqPVTfOPuGWigBH9+tGtxAfUfgk47dX0Gdmagxi+On3jbvzwS+T5LmXAQbGRRCqFApoV5v/hR QiQmTlAX2a5KDnvWGo9C+mJRuVFF3VW66zhj3Phxc9CTQXKWiu0wjBJHub1YOOHl7NqM5GXZa1CqU AnFiK1nhSUDWFA==; In-Reply-To: (message from Gerd =?utf-8?Q?M?= =?utf-8?Q?=C3=B6llmann?= on Wed, 08 Jan 2025 15:08:34 +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:327793 Archived-At: > From: Gerd Möllmann > Cc: pipcet@protonmail.com, emacs-devel@gnu.org > Date: Wed, 08 Jan 2025 15:08:34 +0100 > > Eli Zaretskii writes: > > > 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. > > Well what I said is what I perceived. I believe you. Which is why I tried to explain the state of affairs as I see them. > What about your request to discuss changes on the branch before > committing? Is that off the table? I asked that about the patch which xstrdup's strings before putting them into SAFE_NALLOCA'd array in callproc.c. That was discussed enough, and now is installed, so that issue is closed, from where I stand. I also asked to discuss each place where you suggest replacing SAFE_ALLOCA and its ilk -- is that what you are asking about?