reorg to allow taking content lock
The lock will only persist during the perform stage, so the content must be removed from the annex then, rather than in the cleanup stage. (No lock is actually taken yet.)
This commit is contained in:
parent
58563c5b1a
commit
8ce7e73f74
5 changed files with 54 additions and 26 deletions
|
@ -38,6 +38,10 @@ distinguishable from "not in annex".
|
|||
|
||||
---
|
||||
|
||||
drop --from could also cycle. Locking should fix.
|
||||
|
||||
---
|
||||
|
||||
move --to can also be included in the cycle, since it can drop data.
|
||||
|
||||
Consider move to a remote that already has the content and
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue