From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 46916@debbugs.gnu.org, pipcet@gmail.com
Subject: bug#46916: 28.0.50; pure_alloc(10424, ...) fails badly when pure space is exhausted
Date: Fri, 5 Nov 2021 00:11:16 -0700 [thread overview]
Message-ID: <CADwFkmmoeG-a=xAEuJJ=Ty+kr07HV7sq1grRfRQG-R75nnrD4w@mail.gmail.com> (raw)
In-Reply-To: <831r41nuhr.fsf@gnu.org>
tags 46916 wontfix
close 46916
thanks
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Stefan Kangas <stefan@marxist.se>
>> Date: Sun, 31 Oct 2021 07:02:47 -0700
>> Cc: Eli Zaretskii <eliz@gnu.org>, 46916@debbugs.gnu.org
>>
>> Eli, I'm not sure if your previous reply was just intended to say "we
>> normally just increase the size of purespace", or if you also object to
>> installing this patch?
>
> I don't see a need for anything more complex than enlarging the pure
> space, yes. in fact, I don't even see a reason to enlarge the pure
> space, since no one else reported a problem with the existing amount
> of pure space.
OK, so I'm closing this bug as wontfix. I somewhat agree with Pip Cet
that we could just fix this, but given that the plan is to eventually
remove purespace, we also might as well leave it all alone.
prev parent reply other threads:[~2021-11-05 7:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 12:24 bug#46916: 28.0.50; pure_alloc(10424, ...) fails badly when pure space is exhausted Pip Cet
2021-03-04 12:44 ` Pip Cet
2021-03-04 14:15 ` Eli Zaretskii
2021-10-31 2:56 ` Stefan Kangas
2021-10-31 7:13 ` Eli Zaretskii
2021-10-31 9:41 ` Pip Cet
2021-10-31 11:29 ` Eli Zaretskii
2021-10-31 14:02 ` Stefan Kangas
2021-10-31 14:23 ` Eli Zaretskii
2021-11-05 7:11 ` Stefan Kangas [this message]
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='CADwFkmmoeG-a=xAEuJJ=Ty+kr07HV7sq1grRfRQG-R75nnrD4w@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=46916@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=pipcet@gmail.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).