[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
grep branch, master, updated. v3.3-57-g7163583
From: |
Paul Eggert |
Subject: |
grep branch, master, updated. v3.3-57-g7163583 |
Date: |
Mon, 30 Dec 2019 03:58:23 -0500 (EST) |
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "grep".
The branch, master has been updated
via 71635837d14c842ceb8a0c096b52656936ac4965 (commit)
from bc5ac38040eb49c751e39700651f2b98cd866228 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
http://git.savannah.gnu.org/cgit/grep.git/commit/?id=71635837d14c842ceb8a0c096b52656936ac4965
commit 71635837d14c842ceb8a0c096b52656936ac4965
Author: Paul Eggert <address@hidden>
Date: Mon Dec 30 00:58:03 2019 -0800
doc: fix bug# typo
diff --git a/doc/grep.texi b/doc/grep.texi
index 8866ec4..13b8df0 100644
--- a/doc/grep.texi
+++ b/doc/grep.texi
@@ -1989,7 +1989,7 @@ 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 23522, with little sign of forthcoming fixes. Luckily,
+and 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.
-----------------------------------------------------------------------
Summary of changes:
doc/grep.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
grep
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- grep branch, master, updated. v3.3-57-g7163583,
Paul Eggert <=