[BUG] git grep broken on master - won't work when merging
From: Martin Langhoff <hidden>
Date: 2016-06-15 22:43:47
Subsystem:
the rest · Maintainer:
Linus Torvalds
Strange behaviour of git grep on one of the projects I hack on... $ git --version git version 1.5.3.5.561.g140d $ git grep LOB lib fatal: insanely many options to grep After a bit of head-scratching I realised I was in the middle of a merge, with some unresolved paths in the lib directory. A bit of testing shows that the unresolved index is probably the problem: $ git grep LOB lib fatal: insanely many options to grep # an unresolved file $ git grep LOB lib/accesslib.php fatal: insanely many options to grep $ git grep --cached LOB lib (... expected grep output...) $ git reset --hard $ git grep LOB lib (... expected grep output...) ... not sure what the correct behaviour should be -- I guess the most reasonable action would be to grep the files on disk for those unresolved paths. In any case, the error message is insanely many confusing to user! ;-) Probably whitespace damaged...
diff --git a/builtin-grep.c b/builtin-grep.c
index c7b45c4..1831ef0 100644
--- a/builtin-grep.c
+++ b/builtin-grep.c@@ -213,7 +213,7 @@ static int flush_grep(struct grep_opt *opt, * arguments even for the call in the main loop. */ if (kept) - die("insanely many options to grep"); + die("Unresolved index or too many options to grep"); /* * If we have two or more paths, we do not have to do
cheers, martin