From: Karl Berry <karl@freefriends.org>
To: bug-gnulib@gnu.org
Subject: scratch_buffer.h, scratch_buffer_dupfree.c sync
Date: Wed, 2 Nov 2022 16:37:06 -0600 [thread overview]
Message-ID: <202211022237.2A2Mb6uK000339@freefriends.org> (raw)
1) LIBC/include/scratch_buffer.h has introduced some substantial changes
over GNULIB/lib/malloc/scratch_buffer.h. I'm not sure if it is safe
to sync them any more. Especially because:
2) LIBC/nalloc/scratch_buffer_dupfree.c no longer exists. There is no
such file in libc any more.
Paul, anyone, please advise. -k
next reply other threads:[~2022-11-02 22:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 22:37 Karl Berry [this message]
2022-11-03 1:18 ` scratch_buffer.h, scratch_buffer_dupfree.c sync Paul Eggert
2022-11-03 2:37 ` Bruno Haible
2022-11-03 3:09 ` Paul Eggert
2022-11-03 10:51 ` Bruno Haible
2022-11-03 11:03 ` Florian Weimer
2022-11-03 12:41 ` Bruno Haible
2022-11-03 18:27 ` Paul Eggert
2022-11-03 20:44 ` Bruno Haible
2022-11-03 18:26 ` Paul Eggert
2022-11-03 19:37 ` Florian Weimer
2022-11-03 20:40 ` Karl Berry
2022-11-03 21:12 ` 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=202211022237.2A2Mb6uK000339@freefriends.org \
--to=karl@freefriends.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).