From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: pipcet@protonmail.com, emacs-devel@gnu.org
Subject: Re: scratch/igc: Avoid MPS being interrupted by signals
Date: Wed, 08 Jan 2025 15:46:05 +0100 [thread overview]
Message-ID: <m24j29pdn6.fsf@gmail.com> (raw)
In-Reply-To: <86v7up2xus.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 08 Jan 2025 16:18:03 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> 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?
Yes, these. Long draining threads with indefinite outcome, from my POV,
It's good to hear now that you got something out of this you wanted to
know. But I would have found it nice if you would let me know. Others
too of course.
Or we let things just happen, discuss only if there are concrete
questions, or whatever. I don't know either. Main thing for me is to
avoid endless palaver where everyone is a bit dumber and drained in the
end.
next prev parent reply other threads:[~2025-01-08 14:46 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
2025-01-08 14:08 ` Gerd Möllmann
2025-01-08 14:18 ` Eli Zaretskii
2025-01-08 14:46 ` Gerd Möllmann [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m24j29pdn6.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=eliz@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.