summaryrefslogtreecommitdiff
path: root/git-add--interactive.perl
diff options
context:
space:
mode:
authorJeff King <peff@peff.net>2010-02-16 07:03:16 (GMT)
committerJunio C Hamano <gitster@pobox.com>2010-02-16 17:03:58 (GMT)
commit003c6abdb27c367747847a76b0a7890d67c794be (patch)
treec4410379462761a7cac69246521f806d31deac0c /git-add--interactive.perl
parent460ccd0e19774fd5e4f69de5a454068c686ac5a6 (diff)
downloadgit-003c6abdb27c367747847a76b0a7890d67c794be.zip
git-003c6abdb27c367747847a76b0a7890d67c794be.tar.gz
git-003c6abdb27c367747847a76b0a7890d67c794be.tar.bz2
dwim_ref: fix dangling symref warning
If we encounter a symref that is dangling, in most cases we will warn about it. The one exception is a dangling HEAD, as that indicates a branch yet to be born. However, the check in dwim_ref was not quite right. If we were fed something like "HEAD^0" we would try to resolve "HEAD", see that it is dangling, and then check whether the _original_ string we got was "HEAD" (which it wasn't in this case). And that makes no sense; the dangling thing we found was not "HEAD^0" but rather "HEAD". Fixing this squelches a scary warning from "submodule summary HEAD" (and consequently "git status" with status.submodulesummary set) in an empty repo, as the submodule script calls "git rev-parse -q --verify HEAD^0". Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-add--interactive.perl')
0 files changed, 0 insertions, 0 deletions