From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: pipcet@protonmail.com, emacs-devel@gnu.org
Subject: Re: Pure space
Date: Sat, 17 Aug 2024 13:45:49 +0300 [thread overview]
Message-ID: <86frr32zs2.fsf@gnu.org> (raw)
In-Reply-To: <87r0ank1hq.fsf@yahoo.com> (message from Po Lu on Sat, 17 Aug 2024 16:16:49 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Sat, 17 Aug 2024 16:16:49 +0800
>
> Pip Cet <pipcet@protonmail.com> writes:
>
> > So, even if the decision is to keep pure space, can we at least make
> > pure space overflow a fatal condition?
>
> Can't pure space be eliminated without affecting unexec?
Maybe it could, but I'm not interested in investing any development
efforts in the unexec builds. So, as already discussed and decided
long ago, if we want to remove the pure space, unexec will need to go
with it.
next prev parent reply other threads:[~2024-08-17 10:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 19:07 Pure space Pip Cet
2024-08-17 6:18 ` Eli Zaretskii
2024-08-17 6:59 ` Stefan Kangas
2024-08-17 8:14 ` Po Lu
2024-08-17 12:10 ` Stefan Kangas
2024-08-17 12:53 ` Eli Zaretskii
2024-08-17 13:36 ` Po Lu
2024-08-17 14:12 ` Eli Zaretskii
2024-08-17 8:45 ` Pip Cet
2024-08-17 10:51 ` Eli Zaretskii
2024-08-17 11:38 ` Pip Cet
2024-08-17 13:13 ` Eli Zaretskii
2024-08-17 13:26 ` Pip Cet
2024-08-17 14:29 ` Eli Zaretskii
2024-08-17 14:35 ` Pip Cet
2024-08-17 13:11 ` Stefan Kangas
2024-08-17 14:30 ` Pip Cet
2024-08-17 15:34 ` Andrea Corallo
2024-08-17 15:41 ` Pip Cet
2024-08-17 8:16 ` Po Lu
2024-08-17 8:28 ` Po Lu
2024-08-17 8:31 ` Po Lu
2024-08-17 8:57 ` Pip Cet
2024-08-17 11:06 ` Eli Zaretskii
2024-08-17 10:45 ` Eli Zaretskii [this message]
2024-08-17 11:46 ` Po Lu
2024-08-17 12:49 ` Eli Zaretskii
2024-08-17 13:44 ` Po Lu
2024-08-17 14:17 ` Eli Zaretskii
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=86frr32zs2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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 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.