git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] git-grep: document --and, --or, --not, ( and )

From
MLMatthias Lederhofer <matled@gmx.net>
Date
Aug 2, 2006, 22:04 UTC
Message-ID
<E1G8Opk-0003lj-Q7@moooo.ath.cx>
Signed-off-by: Matthias Lederhofer <matled@gmx.net>
---
The synopsis looks a bit strange, perhaps someone else has an idea for
this.
---
 Documentation/git-grep.txt |   11 +++++++++--
 1 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-grep.txt b/Documentation/git-grep.txt
index 62a8e7f..544ad24 100644
--- a/Documentation/git-grep.txt
+++ b/Documentation/git-grep.txt
@@ -16,7 +16,7 @@ SYNOPSIS
 	   [-n] [-l | --files-with-matches] [-L | --files-without-match]
 	   [-c | --count]
 	   [-A <post-context>] [-B <pre-context>] [-C <context>]
-	   [-f <file>] [-e] <pattern>
+	   [-f <file>] [-e] <pattern> [--and|--or|--not|(|)|-e <pattern>...]
 	   [<tree>...]
 	   [--] [<path>...]
 
@@ -74,7 +74,14 @@ OPTIONS
 -e::
 	The next parameter is the pattern. This option has to be
 	used for patterns starting with - and should be used in
-	scripts passing user input to grep.
+	scripts passing user input to grep.  Multiple patterns are
+	combined by 'or'.
+
+--and | --or | --not | ( | )::
+	Specify how multiple patterns are combined using boolean
+	expressions.  `--or` is the default operator.  `--and` has
+	higher precedence than `--or`.  `-e` has to be used for all
+	patterns.
 
 `<tree>...`::
 	Search blobs in the trees for specified patterns.
-- 
1.4.2.rc2.g4713
Message 1 of 1 in “git-grep: document --and, --or, --not, ( and )”
  1. git-grep: document --and, --or, --not, ( and )Matthias Lederhofer, Aug 2, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.