grep branch, master, updated. v3.9-8-g15f1f50

[Paul Eggert]

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  15f1f50e20e7bf615f338a6e064955fff9e4ab67 (commit)
      from  98ee05b4ddfee5c1db2248bdb060a2cd64bf75fa (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=15f1f50e20e7bf615f338a6e064955fff9e4ab67


commit 15f1f50e20e7bf615f338a6e064955fff9e4ab67
Author: Paul Eggert <eggert@cs.ucla.edu>
Date:   Mon Mar 20 00:20:05 2023 -0700

    doc: clarify BRE vs ERE (bug#62272)

diff --git a/doc/grep.in.1 b/doc/grep.in.1
index edc4bc7..f7b8a03 100644
--- a/doc/grep.in.1
+++ b/doc/grep.in.1
@@ -715,12 +715,12 @@ This can cause a performance penalty.
 .BR \-U ", " \-\^\-binary
 Treat the file(s) as binary.
 By default, under MS-DOS and MS-Windows,
-.BR grep
+.B grep
 guesses whether a file is text or binary as described for the
 .B \-\^\-binary\-files
 option.
 If
-.BR grep
+.B grep
 decides the file is a text file, it strips the CR characters from the
 original file contents (to make regular expressions with
 .B ^
@@ -756,13 +756,14 @@ expressions, by using various operators to combine 
smaller expressions.
 understands three different versions of regular expression syntax:
 \*(lqbasic\*(rq (BRE), \*(lqextended\*(rq (ERE) and \*(lqperl\*(rq (PCRE).
 In GNU
-.B grep
-there is no difference in available functionality between basic and
-extended syntax.
-In other implementations, basic regular expressions are less powerful.
+.BR grep ,
+basic and extended regular expressions are merely different notations
+for the same pattern-matching functionality.
+In other implementations, basic regular expressions are ordinarily
+less powerful than extended, though occasionally it is the other way around.
 The following description applies to extended regular expressions;
 differences for basic regular expressions are summarized afterwards.
-Perl-compatible regular expressions give additional functionality, and are
+Perl-compatible regular expressions have different functionality, and are
 documented in
 .BR pcre2syntax (3)
 and
diff --git a/doc/grep.texi b/doc/grep.texi
index 7a00add..4ed9782 100644
--- a/doc/grep.texi
+++ b/doc/grep.texi
@@ -1190,12 +1190,13 @@ by using various operators to combine smaller 
expressions.
 three different versions of regular expression syntax:
 basic (BRE), extended (ERE), and Perl-compatible (PCRE).
 In GNU @command{grep},
-there is no difference in available functionality between basic and
-extended syntax.
-In other implementations, basic regular expressions are less powerful.
+basic and extended regular expressions are merely different notations
+for the same pattern-matching functionality.
+In other implementations, basic regular expressions are ordinarily
+less powerful than extended, though occasionally it is the other way around.
 The following description applies to extended regular expressions;
 differences for basic regular expressions are summarized afterwards.
-Perl-compatible regular expressions give additional functionality, and
+Perl-compatible regular expressions have different functionality, and
 are documented in the @i{pcre2syntax}(3) and @i{pcre2pattern}(3) manual
 pages, but work only if PCRE is available in the system.
 

-----------------------------------------------------------------------

Summary of changes:
 doc/grep.in.1 | 15 ++++++++-------
 doc/grep.texi |  9 +++++----
 2 files changed, 13 insertions(+), 11 deletions(-)


hooks/post-receive
-- 
grep