summaryrefslogtreecommitdiff
path: root/t/t5515/fetch.br-config-explicit-merge
diff options
context:
space:
mode:
authorLibravatar Nguyễn Thái Ngọc Duy <pclouds@gmail.com>2015-12-21 17:22:52 +0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2015-12-22 13:36:47 -0800
commitdf1e6ea87a58fc8d029efb3041d851f7d6653a1d (patch)
treef84a525421c7b26646466f2e85e8586d12fa6479 /t/t5515/fetch.br-config-explicit-merge
parentsetup: set env $GIT_WORK_TREE when work tree is set, like $GIT_DIR (diff)
downloadtgif-df1e6ea87a58fc8d029efb3041d851f7d6653a1d.tar.xz
Revert "setup: set env $GIT_WORK_TREE when work tree is set, like $GIT_DIR"
This reverts d95138e6 (setup: set env $GIT_WORK_TREE when work tree is set, like $GIT_DIR, 2015-06-26). It has caused three regression reports so far. http://article.gmane.org/gmane.comp.version-control.git/281608 http://article.gmane.org/gmane.comp.version-control.git/281979 http://article.gmane.org/gmane.comp.version-control.git/282691 All of them are about spawning git subprocesses, where the new presence of GIT_WORK_TREE either changes command behaviour (git-init or git-clone), or how repo/worktree is detected (from aliases), with or without $GIT_DIR. The original bug will be re-fixed another way. Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5515/fetch.br-config-explicit-merge')
0 files changed, 0 insertions, 0 deletions