summaryrefslogtreecommitdiff
path: root/sha1_name.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@osdl.org>2005-08-13 10:50:56 -0700
committerJunio C Hamano <junkio@cox.net>2005-08-13 18:28:50 -0700
commit02a4a32c2da9a89eb9ebc58325adcb47775c9ed5 (patch)
tree87bf551ac035553ae59efa15d018a7d41a9bbf0c /sha1_name.c
parent314082512403f7f6969cc6d5ded4a48c68a9962e (diff)
downloadgit-02a4a32c2da9a89eb9ebc58325adcb47775c9ed5.tar.gz
[PATCH] Make sure git-resolve-script always works on commits
You can resolve a tag, and it does the right thing except that it might end up writing the tag itself into the resulting HEAD, which will confuse subsequent operations no end. This makes sure that when we resolve two heads, we will have turned them into proper commits before we start acting on them. This also fixes the parsing of "treeish^0", which would incorrectly resolve to "treeish" instead of causing an error. Signed-off-by: Linus Torvalds <torvalds@osdl.org> Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'sha1_name.c')
-rw-r--r--sha1_name.c10
1 files changed, 3 insertions, 7 deletions
diff --git a/sha1_name.c b/sha1_name.c
index 5d1e441e5a..df45b172a3 100644
--- a/sha1_name.c
+++ b/sha1_name.c
@@ -208,13 +208,9 @@ static int get_sha1_1(const char *name, int len, unsigned char *sha1)
} else
parent = -1;
- if (0 <= parent) {
- ret = get_parent(name, len, sha1, parent);
- if (!ret)
- return 0;
- else if(parent>0)
- return ret;
- }
+ if (parent >= 0)
+ return get_parent(name, len, sha1, parent);
+
ret = get_sha1_basic(name, len, sha1);
if (!ret)
return 0;