summaryrefslogtreecommitdiff
path: root/Messages
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-05-19 14:26:07 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-05-19 14:26:07 -0400
commita5351d739d86513973b82aaabe58f7d1c5f829ea (patch)
tree608e3f38da179aa2af4d1e46d0cb43f29dfb88fb /Messages
parent2e819796cdfdfccb2ebef7b10e2653e58d832d83 (diff)
fix inAnnexSafe result for direct file that is being dropped
It was returning Just False in this situation, which differed from indirect mode behavior. I don't think this led to any actual problems; things that checked if the file being dropped was present just failed to fail, and instead reported it wasn't present, possibly incorrectly. Hmm, it's possible that this could have made git annex fsck --from remote update the location log wrongly, if a remote was in direct mode, and was in the middle of trying to drop a key, and the drop later failed.
Diffstat (limited to 'Messages')
0 files changed, 0 insertions, 0 deletions