From: Paul Eggert <eggert@cs.ucla.edu>
To: bug-gnulib@gnu.org
Cc: Paul Eggert <eggert@cs.ucla.edu>
Subject: [PATCH] regex: now back in sync with glibc
Date: Wed, 6 Nov 2019 12:14:22 -0800 [thread overview]
Message-ID: <20191106201422.494880-1-eggert@cs.ucla.edu> (raw)
* config/srclist.txt: regcomp.c, regex_internal.c, regex_internal.h,
regexec.c got merged into glibc and are now copies again.
---
ChangeLog | 6 ++++++
config/srclist.txt | 8 ++++----
2 files changed, 10 insertions(+), 4 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index b20008a17..1400624d4 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2019-11-06 Paul Eggert <eggert@cs.ucla.edu>
+
+ regex: now back in sync with glibc
+ * config/srclist.txt: regcomp.c, regex_internal.c, regex_internal.h,
+ regexec.c got merged into glibc and are now copies again.
+
2019-10-27 Bruno Haible <bruno@clisp.org>
host-cpu-c-abi: Recognize i386 and a couple of other CPUs as 32-bit.
diff --git a/config/srclist.txt b/config/srclist.txt
index e001d15c3..4a3a5a7af 100644
--- a/config/srclist.txt
+++ b/config/srclist.txt
@@ -52,12 +52,12 @@ $LIBCSRC malloc/scratch_buffer_grow_preserve.c lib/malloc
$LIBCSRC malloc/scratch_buffer_set_array_size.c lib/malloc
# Temporarily newer in Gnulib than in glibc.
#$LIBCSRC include/intprops.h lib
-#$LIBCSRC posix/regcomp.c lib
+$LIBCSRC posix/regcomp.c lib
$LIBCSRC posix/regex.c lib
$LIBCSRC posix/regex.h lib
-#$LIBCSRC posix/regex_internal.c lib
-#$LIBCSRC posix/regex_internal.h lib
-#$LIBCSRC posix/regexec.c lib
+$LIBCSRC posix/regex_internal.c lib
+$LIBCSRC posix/regex_internal.h lib
+$LIBCSRC posix/regexec.c lib
$LIBCSRC time/timegm.c lib
$LIBCSRC time/mktime.c lib
$LIBCSRC time/mktime-internal.h lib
--
2.23.0
reply other threads:[~2019-11-06 20:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20191106201422.494880-1-eggert@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--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).