summaryrefslogtreecommitdiff
path: root/copy.c
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2015-05-19 13:17:52 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2015-05-19 13:17:52 -0700
commit1645dbeff75d466230eb54b8548cfe9c9dcc9e5e (patch)
tree6066d55942a8be5f515b9fd97b09dde803928a81 /copy.c
parentMerge branch 'jc/gitignore-precedence' (diff)
parentstop putting argv[0] dirname at front of PATH (diff)
downloadtgif-1645dbeff75d466230eb54b8548cfe9c9dcc9e5e.tar.xz
Merge branch 'jk/git-no-more-argv0-path-munging'
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 'copy.c')
0 files changed, 0 insertions, 0 deletions