mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

design done

Browse source
This commit is contained in:
Joey Hess 2020-10-19 14:57:02 -04:00
parent 5009c1ce68
commit 15ea0e6c0a
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 13 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

13
doc/todo/interruped_move_resume.mdwn
View file

@ -10,6 +10,9 @@ numcopies is 2, so it can't drop the copy from the remote.
This happens to me often enough to be annoying. This happens to me often enough to be annoying.
I think it can also happen with move --to, although I can't remember seeing
that.
Perhaps some local state could avoid this problem? Perhaps some local state could avoid this problem?
--[[Joey]] --[[Joey]]
@ -48,3 +51,13 @@ Perhaps some local state could avoid this problem?
> > Still, if the move is interrupted and never resumed, after a sync > > Still, if the move is interrupted and never resumed, after a sync
> > with the remote, the only copy appears missing, which does seem > > with the remote, the only copy appears missing, which does seem
> > potentially confusing. > > potentially confusing.
> Local state could be a file listing keys that have had a move started
> but not finished. When doing the same move, it should be allowed to
> succeed even if numcopies would prevent it. More accurately, it
> should disregard the local copy when checking numcopies for a move
> --from. And for a move --to, it should disregard the remote copy.
> May need 2 separate lists for the two kinds of moves.
>
> > This is complex to implement, but it avoids the gotchas in the earlier
> > ideas, so I think is best. --[[Joey]]