path: root/
diff options
authorJunio C Hamano <>2009-11-23 23:56:32 (GMT)
committerJunio C Hamano <>2009-11-24 00:31:07 (GMT)
commite1622bfcbad680225ad5c337e4778df88389227e (patch)
tree9a652f7a3e3a2999dd8469ddd6bbedda05cb3d36 /
parent7b1042292d5dc18508213c3be888b740d02f02e3 (diff)
Protect scripted Porcelains from GREP_OPTIONS insanity
If the user has exported the GREP_OPTIONS environment variable, the output from "grep" and "egrep" in scripted Porcelains may be different from what they expect. For example, we may want to count number of matching lines, by "grep" piped to "wc -l", and GREP_OPTIONS=-C3 will break such use. The approach taken by this change to address this issue is to protect only our own use of grep/egrep. Because we do not unset it at the beginning of our scripts, hook scripts run from the scripted Porcelains are exposed to the same insanity this environment variable causes when grep/egrep is used to implement logic (e.g. "grep | wc -l"), and it is entirely up to the hook scripts to protect themselves. On the other hand, applypatch-msg hook may want to show offending words in the proposed commit log message using grep to the end user, and the user might want to set GREP_OPTIONS=--color to paint the match more visibly. The approach to protect only our own use without unsetting the environment variable globally will allow this use case. Signed-off-by: Junio C Hamano <>
Diffstat (limited to '')
1 files changed, 8 insertions, 0 deletions
diff --git a/ b/
index c41c2f7..aa07cc3 100755
--- a/
+++ b/
@@ -114,6 +114,14 @@ git_editor() {
eval "${GIT_EDITOR:=vi}" '"$@"'
+sane_grep () {
+ GREP_OPTIONS= LC_ALL=C grep "$@"
+sane_egrep () {
+ GREP_OPTIONS= LC_ALL=C egrep "$@"
is_bare_repository () {
git rev-parse --is-bare-repository