fetch: report local storage errors in status table
commit6315472eed9ff5f594560ddfd592ea21c665fe96
authorJeff King <peff@peff.net>
Fri, 27 Jun 2008 03:59:50 +0000 (26 23:59 -0400)
committerJunio C Hamano <gitster@pobox.com>
Fri, 27 Jun 2008 23:22:51 +0000 (27 16:22 -0700)
tree2ff108b863ac0721ccea94d254824af776614bc4
parent7ac749c96d143ba4f76723959892cbaddbe8ed07
fetch: report local storage errors in status table

Previously, if there was an error while storing a local
tracking ref, the low-level functions would report an error,
but fetch's status output wouldn't indicate any problem.
E.g., imagine you have an old "refs/remotes/origin/foo/bar" but
upstream has deleted "foo/bar" in favor of a new branch
"foo". You would get output like this:

  error: there are still refs under 'refs/remotes/origin/foo'
  From $url_of_repo
   * [new branch]      foo        -> origin/foo

With this patch, the output takes into account the status of
updating the local ref:

  error: there are still refs under 'refs/remotes/origin/foo'
  From $url_of_repo
   ! [new branch]      foo        -> origin/foo  (unable to update local ref)

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
builtin-fetch.c