summaryrefslogtreecommitdiff
path: root/t/t7605-merge-resolve.sh
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2015-05-26 13:49:18 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2015-05-26 13:49:18 -0700
commitaf6d7a6231c30bb8bb7220085edb574e540bfa19 (patch)
tree76266cd491f9237283a2a56b0f7cc84205e152ca /t/t7605-merge-resolve.sh
parentGit 2.4.1 (diff)
parentstop putting argv[0] dirname at front of PATH (diff)
downloadtgif-af6d7a6231c30bb8bb7220085edb574e540bfa19.tar.xz
Merge branch 'jk/git-no-more-argv0-path-munging' into maint
We have prepended $GIT_EXEC_PATH and the path "git" is installed in (typically "/usr/bin") to $PATH when invoking subprograms and hooks for almost eternity, but the original use case the latter tried to support was semi-bogus (i.e. install git to /opt/foo/git and run it without having /opt/foo on $PATH), and more importantly it has become less and less relevant as Git grew more mainstream (i.e. the users would _want_ to have it on their $PATH). Stop prepending the path in which "git" is installed to users' $PATH, as that would interfere the command search order people depend on (e.g. they may not like versions of programs that are unrelated to Git in /usr/bin and want to override them by having different ones in /usr/local/bin and have the latter directory earlier in their $PATH). * jk/git-no-more-argv0-path-munging: stop putting argv[0] dirname at front of PATH
Diffstat (limited to 't/t7605-merge-resolve.sh')
0 files changed, 0 insertions, 0 deletions