CVSROOT: /webcvs/grep Module name: grep Changes by: Jim Meyering <meyering> 20/09/27 23:36:49
Index: html_node/Known-Bugs.html =================================================================== RCS file: /webcvs/grep/grep/manual/html_node/Known-Bugs.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -b -r1.1 -r1.2 --- html_node/Known-Bugs.html 2 Jan 2020 23:18:44 -0000 1.1 +++ html_node/Known-Bugs.html 28 Sep 2020 03:36:49 -0000 1.2 @@ -14,10 +14,10 @@ <!-- Created by GNU Texinfo 6.5, http://www.gnu.org/software/texinfo/ --> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> -<title>Known Bugs (GNU Grep 3.4)</title> +<title>Known Bugs (GNU Grep 3.5)</title> -<meta name="description" content="Known Bugs (GNU Grep 3.4)"> -<meta name="keywords" content="Known Bugs (GNU Grep 3.4)"> +<meta name="description" content="Known Bugs (GNU Grep 3.5)"> +<meta name="keywords" content="Known Bugs (GNU Grep 3.5)"> <meta name="resource-type" content="document"> <meta name="distribution" content="global"> <meta name="Generator" content="makeinfo"> @@ -82,9 +82,15 @@ 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 +<a href="https://sourceware.org/bugzilla/";>GNU C library bug database</a> +contained back-reference bugs +<a href="https://sourceware.org/bugzilla/show_bug.cgi?id=52";>52</a>, +<a href="https://sourceware.org/bugzilla/show_bug.cgi?id=10844";>10844</a>, +<a href="https://sourceware.org/bugzilla/show_bug.cgi?id=11053";>11053</a>, +<a href="https://sourceware.org/bugzilla/show_bug.cgi?id=24269";>24269</a> +and <a href="https://sourceware.org/bugzilla/show_bug.cgi?id=25322";>25322</a>, +with little sign of forthcoming fixes. Luckily, back-references are rarely useful and it should be little trouble to avoid them in practical applications. </p>
