![[tokkee]](http://tokkee.org/images/avatar.png){kind=avatar}
| author | Junio C Hamano <gitster@pobox.com> | |
| Thu, 3 Nov 2011 19:15:08 +0000 (12:15 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 3 Nov 2011 21:27:04 +0000 (14:27 -0700) | ||
| commit | ee6dfb2d83ba1b057943e705f707fa27e34e47f9 | |
| tree | 538d0e0e2f1cf2e8586bfc671ca61dbea70f5d46 | tree | snapshot |
| parent | db85b3a74fd1c50f007c198e4dc7265fdc1f2749 | commit | diff |
receive-pack: do not expect object 0{40} to exist
When pushing to delete a ref, it uses 0{40} as an object name to signal
that the request is a deletion. We shouldn't trigger "deletion of a
corrupt ref" warning in such a case, which was designed to notice that a
ref points at an object that is truly missing from the repository.
Reported-by: Stefan Näwe
Signed-off-by: Junio C Hamano <gitster@pobox.com>
When pushing to delete a ref, it uses 0{40} as an object name to signal
that the request is a deletion. We shouldn't trigger "deletion of a
corrupt ref" warning in such a case, which was designed to notice that a
ref points at an object that is truly missing from the repository.
Reported-by: Stefan Näwe
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin/receive-pack.c | diff | blob | history |