From: Jeff King <peff@peff.net>
Date: Fri, 27 Jun 2008 03:57:47 GMT
Subject: Re: bug related to branches using / in name
Message-ID: <20080627035747.GC7144@sigill.intra.peff.net>
In-Reply-To: <20080627030245.GA7144@sigill.intra.peff.net>

On Thu, Jun 26, 2008 at 11:02:46PM -0400, Jeff King wrote:

> It might be nicer if this were handled automatically, but it would
> violate git-fetch's rule about never deleting branches. And presumably
> this comes up infrequently enough that it isn't a problem. Perhaps a
> better error message suggesting git-prune might make sense?

And here is a 2-patch series improving the error reporting for this
case (and it also helps with some other cases). I'm a little iffy on
2/2, since we don't actually _know_ that remote pruning will help. But
propagating specific errors up through the call chain would require
reasonably major surgery.

  1/2: fetch: give a hint to the user when local refs fail to update
  2/2: fetch: report local storage errors in status table

-Peff