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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
