summaryrefslogtreecommitdiff
path: root/t/t9165-git-svn-fetch-merge-branch-of-branch.sh
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2014-05-15 04:54:06 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2014-05-15 10:03:06 -0700
commitd6c8a05bd58be82165be54f01c861c0fae28b8c4 (patch)
tree73bb7ff3e864bef7ae92281061d982186879abc0 /t/t9165-git-svn-fetch-merge-branch-of-branch.sh
parentGit 1.8.5.5 (diff)
downloadtgif-d6c8a05bd58be82165be54f01c861c0fae28b8c4.tar.xz
open_sha1_file: report "most interesting" errno
When we try to open a loose object file, we first attempt to open in the local object database, and then try any alternates. This means that the errno value when we return will be from the last place we looked (and due to the way the code is structured, simply ENOENT if we do not have have any alternates). This can cause confusing error messages, as read_sha1_file checks for ENOENT when reporting a missing object. If errno is something else, we report that. If it is ENOENT, but has_loose_object reports that we have it, then we claim the object is corrupted. For example: $ chmod 0 .git/objects/??/* $ git rev-list --all fatal: loose object b2d6fab18b92d49eac46dc3c5a0bcafabda20131 (stored in .git/objects/b2/d6fab18b92d49eac46dc3c5a0bcafabda20131) is corrupt This patch instead keeps track of the "most interesting" errno we receive during our search. We consider ENOENT to be the least interesting of all, and otherwise report the first error found (so problems in the object database take precedence over ones in alternates). Here it is with this patch: $ git rev-list --all fatal: failed to read object b2d6fab18b92d49eac46dc3c5a0bcafabda20131: Permission denied Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t9165-git-svn-fetch-merge-branch-of-branch.sh')
0 files changed, 0 insertions, 0 deletions