From 5ab3849da36062688daf383f7ffba05c4877565f Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 15 Jul 2020 20:42:53 -0400 Subject: [PATCH] thought --- doc/todo/interruped_move_resume.mdwn | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/doc/todo/interruped_move_resume.mdwn b/doc/todo/interruped_move_resume.mdwn index b4b1bd0288..85ab03cd8f 100644 --- a/doc/todo/interruped_move_resume.mdwn +++ b/doc/todo/interruped_move_resume.mdwn @@ -13,3 +13,15 @@ This happens to me often enough to be annoying. Perhaps some local state could avoid this problem? --[[Joey]] + +> One simple way would be to drop the content from the remote before moving +> it to annex/objects/. Then if the move were interrupted before the drop, +> it could resume the interrupted transfer, and numcopies would work the +> same as it did when the move started. +> +> Or, move to annex/objects/ but delay updating the location tracking to +> say it's in the local repo until after the drop. +> +> Either way, a problem is that the only copy would appear missing until +> the move was re-run. The latter approach at least lets fsck clean up +> from that situation, but it could still be surprising.