summaryrefslogtreecommitdiff
path: root/t/t5515/refs.br-remote-glob_remote-glob
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2008-07-08 00:08:02 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2008-07-08 13:05:11 -0700
commit0b294c0abf00a9cf7468e0ea62722ae23b0816cc (patch)
tree5e424be8dc66b52a104328ee212347aa58811db5 /t/t5515/refs.br-remote-glob_remote-glob
parentMerge branch 'qq/maint' into maint (diff)
downloadtgif-0b294c0abf00a9cf7468e0ea62722ae23b0816cc.tar.xz
make deleting a missing ref more quiet
If git attempts to delete a ref, but the unlink of the ref file fails, we print a message to stderr. This is usually a good thing, but if the error is ENOENT, then it indicates that the ref has _already_ been deleted. And since that's our goal, it doesn't make sense to complain to the user. This harmonizes the error reporting behavior for the unpacked and packed cases; the packed case already printed nothing on ENOENT, but the unpacked printed unconditionally. Additionally, send-pack would, when deleting the tracking ref corresponding to a remote delete, print "Failed to delete" on any failure. This can be a misleading message, since we actually _did_ delete at the remote side, but we failed to delete locally. Rather than make the message more precise, let's just eliminate it entirely; the delete_ref routine already takes care of printing out a much more specific message about what went wrong. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5515/refs.br-remote-glob_remote-glob')
0 files changed, 0 insertions, 0 deletions