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

Added a comment: Try annex.queuesize and --not --in

Browse source
This commit is contained in:
nobodyinperson 2023-12-27 07:51:00 +00:00 committed by admin
parent 59b62e13f9
commit ba85d3e165
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/forum/What_operations_are_safe_to_interrupt__63__/comment_5_8d36d42e34f5deae04bfa83c568b89d5._comment Normal file
View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="nobodyinperson"
avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5"
subject="Try annex.queuesize and --not --in"
date="2023-12-27T07:51:00Z"
content="""
Git annex can normally resume any operation seamlessly. It can resume from aborted copying and shouldn't need to start over. I suggest:
- setting [annex.queuesize](https://git-annex.branchable.com/git-annex/) to a low value to commit more frequently to the `git-annex` branch (I think that it does that)
- skipping already-present files by specifying `git annex --copy --to=slowremote --not --in=slowremote`, that should speed up the initial phase of finding what to copy and also not display the files that are already copied (maybe that confused you)
"""]]