summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2020-01-02 22:11:10 (GMT)
committerPaul Eggert <eggert@cs.ucla.edu>2020-01-02 22:11:32 (GMT)
commit7bec6b13ce4dc01bb50b7fa682e3b77778562399 (patch)
tree2f980680b7c4f5ba7684ea901743e6d87b5f3de1
parent767c83fd302f05a8b790a78eacce11aac50903ee (diff)
downloadgrep-7bec6b13ce4dc01bb50b7fa682e3b77778562399.tar.gz
doc: mention glibc bug 24269
* doc/grep.texi (Known Bugs): Mention glibc bug 24269. Merge formatting/URL changes from Gnulib regex.texi.
-rw-r--r--doc/grep.texi12
1 files changed, 9 insertions, 3 deletions
diff --git a/doc/grep.texi b/doc/grep.texi
index 4b279cc..4b26f9d 100644
--- a/doc/grep.texi
+++ b/doc/grep.texi
@@ -1971,9 +1971,15 @@ and memory to explore. Also, the POSIX specification for
back-references is at times unclear. Furthermore, many regular
expression implementations have back-reference bugs that can cause
programs to return incorrect answers or even crash, and fixing these
-bugs has often been low-priority---for example, as of 2019 the GNU C
-library bug database contained back-reference bugs 52, 10844, 11053,
-and 25322, with little sign of forthcoming fixes. Luckily,
+bugs has often been low-priority: for example, as of 2020 the
+@url{https://sourceware.org/bugzilla/,GNU C library bug database}
+contained back-reference bugs
+@url{https://sourceware.org/bugzilla/show_bug.cgi?id=52,,52},
+@url{https://sourceware.org/bugzilla/show_bug.cgi?id=10844,,10844},
+@url{https://sourceware.org/bugzilla/show_bug.cgi?id=11053,,11053},
+@url{https://sourceware.org/bugzilla/show_bug.cgi?id=24269,,24269}
+and @url{https://sourceware.org/bugzilla/show_bug.cgi?id=25322,,25322},
+with little sign of forthcoming fixes. Luckily,
back-references are rarely useful and it should be little trouble to
avoid them in practical applications.