> +library bug database contained back-reference bugs 52, 10844, 11053,
> +and 23522, with little sign of forthcoming fixes. Luckily,
Let me add URLs. (Not everyone knows the location of the glibc bug tracker
by heart.)
doc: Add URLs.
* doc/regex.texi (Back-reference Operator): Add URLs into glibc bug tracker.
diff --git a/doc/regex.texi b/doc/regex.texi
index bac5816..a417444 100644
--- a/doc/regex.texi
+++ b/doc/regex.texi
@@ -1151,8 +1151,12 @@ 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,
+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},
+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.
