Jeff King <peff@xxxxxxxx> writes: > 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@xxxxxxxx> Makes sense --- thanks. This is something we can have automated tests, isn't it? -- 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
