From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: [PATCH] malloc, realloc: fix recently-introduced #undef typos
Date: Sun, 18 Apr 2021 16:24:29 -0700 [thread overview]
Message-ID: <8c7877c5-2563-a41a-eb29-6d80bbe3ab4b@cs.ucla.edu> (raw)
In-Reply-To: <14990950.dRLnaxrnK9@omega>
On 4/16/21 7:53 PM, Bruno Haible wrote:
>> + malloc, realloc: fix recently-introduced #undef typos
> That must have been more than a typo? It must have been an endless recursion?
Yes, they were typos that caused infloops. But little harm done; I don't
think they escaped into any distributions.
next prev parent reply other threads:[~2021-04-18 23:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 0:07 [PATCH] malloc, realloc: fix recently-introduced #undef typos Paul Eggert
2021-04-17 2:53 ` Bruno Haible
2021-04-18 23:24 ` Paul Eggert [this message]
2021-04-21 18:54 ` Paul Eggert
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://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8c7877c5-2563-a41a-eb29-6d80bbe3ab4b@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
/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.
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).