avoid cleaning up move log when drop from remote fails
authorJoey Hess <joeyh@joeyh.name>
Thu, 9 Jun 2022 19:26:25 +0000 (15:26 -0400)
committerJoey Hess <joeyh@joeyh.name>
Thu, 9 Jun 2022 19:26:25 +0000 (15:26 -0400)
commit6d0b243d9d2fca207c65118447df7a7596ac186d
tree3b6bdd5e77999a331b28965a4ac5737cd2914f99
parent13fc6a9b6ad4f0ee0a783c91825ab7ad35dd2b64
avoid cleaning up move log when drop from remote fails

move: Improve resuming a move that succeeded in transferring the content,
but where dropping failed due to eg a network problem, in cases where
numcopies checks prevented the resumed move from dropping the object from
the source repository.

This was earlier done for moves that got interrupted during the drop stage.

Sponsored-by: Svenne Krap on Patreon
CHANGELOG
Command/Move.hs
doc/bugs/move_that_fails_at_drop_stage_does_not_resume_correctly.mdwn