From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Cc: Karl Berry <karl@freefriends.org>, Florian Weimer <fweimer@redhat.com>
Subject: Re: scratch_buffer.h, scratch_buffer_dupfree.c sync
Date: Wed, 2 Nov 2022 20:09:48 -0700 [thread overview]
Message-ID: <6854fb79-d7ec-615f-81f1-9a192ef52828@cs.ucla.edu> (raw)
In-Reply-To: <3611769.t68216eyJU@nimes>
On 11/2/22 19:37, Bruno Haible wrote:
> In other words, I'm suggesting to rename the modules
> scratch_buffer -> glibc-internal/scratch_buffer
> dynarray -> glibc-internal/dynarray
I don't see any problem with that, since as far as I know the only
current users of the two modules are glibc-related modules in Gnulib
itself. However, if in the future programs find these two modules
useful, I suppose we'll need to rename them back.
The scratch_buffer_dupfree function was added to glibc in 2020 only to
make it easier to sync canonicalize.c with Gnulib at the time. So it is
a bit ironic that removing scratch_buffer_dupfree from Gnulib now would
cause us to in some sense deprecate scratch_buffer.
next prev parent reply other threads:[~2022-11-03 3:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 22:37 scratch_buffer.h, scratch_buffer_dupfree.c sync Karl Berry
2022-11-03 1:18 ` Paul Eggert
2022-11-03 2:37 ` Bruno Haible
2022-11-03 3:09 ` Paul Eggert [this message]
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=6854fb79-d7ec-615f-81f1-9a192ef52828@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=fweimer@redhat.com \
--cc=karl@freefriends.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).