Michael Haggerty 5b2d8d6f21 lock_ref_sha1_basic(): improve diagnostics for ref D/F conflicts ...

If there is a failure to lock a reference that is likely caused by a
D/F conflict (e.g., trying to lock "refs/foo/bar" when reference
"refs/foo" already exists), invoke verify_refname_available() to try
to generate a more helpful error message.

That function might not detect an error. For example, some
non-reference file might be blocking the deletion of an
otherwise-empty directory tree, or there might be a race with another
process that just deleted the offending reference. In such cases,
generate the strerror-based error message like before.

Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>

2015-05-11 11:50:20 -07:00

2.5 KiB

Executable File

Raw Blame History

View Raw