author | Mike Hommey <mh@glandium.org> | |
Fri, 14 Dec 2007 21:18:01 +0000 (22:18 +0100) | ||
committer | Junio C Hamano <gitster@pobox.com> | |
Sat, 15 Dec 2007 05:31:59 +0000 (21:31 -0800) | ||
commit | a096bb18af5b7214d9b87b64ae733d106eb96544 | |
tree | abb43fcc181397e9db77ff0d5fece1b23366d705 | tree | snapshot |
parent | 3b683b91cd78dec027105a2810079eb0b27ab2c0 | commit | diff |
Fix random sha1 in error message in http-fetch and http-push
When a downloaded ref doesn't contain a sha1, the error message displays
a random sha1 because of uninitialized memory. This happens when cloning
a repository that is already a clone of another one, in which case
refs/remotes/origin/HEAD is a symref.
Signed-off-by: Mike Hommey <mh@glandium.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
When a downloaded ref doesn't contain a sha1, the error message displays
a random sha1 because of uninitialized memory. This happens when cloning
a repository that is already a clone of another one, in which case
refs/remotes/origin/HEAD is a symref.
Signed-off-by: Mike Hommey <mh@glandium.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
http-push.c | diff | blob | history | |
http-walker.c | diff | blob | history |