summaryrefslogtreecommitdiff
path: root/http.c
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2009-12-30 08:47:03 (GMT)
committerJunio C Hamano <gitster@pobox.com>2009-12-30 09:05:21 (GMT)
commitcd0f0f68e1074e684a014e1714104693097caabc (patch)
treebd1c1679538183ea922d33bf8f4a1ecc8018906c /http.c
parent952dfc6944b29582482ff50a85c04879406c06ba (diff)
downloadgit-cd0f0f68e1074e684a014e1714104693097caabc.zip
git-cd0f0f68e1074e684a014e1714104693097caabc.tar.gz
git-cd0f0f68e1074e684a014e1714104693097caabc.tar.bz2
reset: unbreak hard resets with GIT_WORK_TREE
Commit 952dfc6 tried to tighten the safety valves for doing a "reset --hard" in a bare repository or outside the work tree, but accidentally broke the case for GIT_WORK_TREE. This patch unbreaks it. Most git commands which need a work tree simply use NEED_WORK_TREE in git.c to die before they get to their cmd_* function. Reset, however, only needs a work tree in some cases, and so must handle the work tree itself. The error that 952dfc6 made was to simply forbid certain operations if the work tree was not set up; instead, we need to do the same thing that NEED_WORK_TREE does, which is to call setup_work_tree(). We no longer have to worry about dying in the non-worktree case, as setup_work_tree handles that for us. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'http.c')
0 files changed, 0 insertions, 0 deletions