removed

diff --git a/doc/forum/What_operations_are_safe_to_interrupt__63__/comment_4_6f537c4909bb53ca036b0f85833672e1._comment b/doc/forum/What_operations_are_safe_to_interrupt__63__/comment_4_6f537c4909bb53ca036b0f85833672e1._comment
deleted file mode 100644 (file)
index 63f4a2e..0000000
--- a/doc/forum/What_operations_are_safe_to_interrupt__63__/comment_4_6f537c4909bb53ca036b0f85833672e1._comment
+++ /dev/null
@@ -1,11 +0,0 @@
-[[!comment format=mdwn
- username="nobodyinperson"
- avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5"
- subject="Try anex.queuesize and --not --in"
- date="2023-12-27T07:50:49Z"
- 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)
-"""]]