aboutsummaryrefslogtreecommitdiff
path: root/git-merge-resolve.sh
diff options
context:
space:
mode:
authorGerrit Pape <pape@smarden.org>2008-05-05 07:43:00 +0000
committerJunio C Hamano <gitster@pobox.com>2008-05-05 17:18:20 -0700
commitee831f7ddfc40e9144208c93e24d20ff0ad69194 (patch)
treebe7a81b489709ead6ebbbb6a0c662dca1f1add84 /git-merge-resolve.sh
parent6233a5210ef64ba31bbf0e867e03e9176e0aace9 (diff)
downloadgit-ee831f7ddfc40e9144208c93e24d20ff0ad69194.tar.gz
git-ee831f7ddfc40e9144208c93e24d20ff0ad69194.tar.xz
git-bisect.sh: don't accidentally override existing branch "bisect"
If a branch named "bisect" or "new-bisect" already was created in the repo by other means than git bisect, doing a git bisect used to override the branch without a warning. Now if the branch "bisect" or "new-bisect" already exists, and it was not created by git bisect itself, git bisect start fails with an appropriate error message. Additionally, if checking out a new bisect state fails due to a merge problem, git bisect cleans up the temporary branch "new-bisect". The accidental override has been noticed by Andres Salomon, reported through http://bugs.debian.org/478647 Signed-off-by: Gerrit Pape <pape@smarden.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-merge-resolve.sh')
0 files changed, 0 insertions, 0 deletions