summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-12-13 12:53:12 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-12-13 12:53:12 -0400
commita98877df3b73aee7d61b99bd4c494f12c0cc05c6 (patch)
treec9fe8b742bb9a8633f2ad69c0b4ad23e400c3b9b /doc
parent1f74ec4f93f80a6b67780b2b7a9cbb81689d3c54 (diff)
response
Diffstat (limited to 'doc')
-rw-r--r--doc/forum/more_intelligent_copy_/comment_2_7b3f5d2e9de4b13de821177db2f57bcd._comment15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/forum/more_intelligent_copy_/comment_2_7b3f5d2e9de4b13de821177db2f57bcd._comment b/doc/forum/more_intelligent_copy_/comment_2_7b3f5d2e9de4b13de821177db2f57bcd._comment
new file mode 100644
index 000000000..474a068b6
--- /dev/null
+++ b/doc/forum/more_intelligent_copy_/comment_2_7b3f5d2e9de4b13de821177db2f57bcd._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2016-12-13T16:51:03Z"
+ content="""
+`git annex copy --fast` has the same behavior as `--not --in REMOTE`
+
+The reason this is not the default behavior is that git-annex's location
+tracking information can sometimes be out of date, and then those
+two will not copy some files despite their content not being any longer
+in the remote. This won't lead to data loss, but could result
+in unexpected behavior, and so the slower, more understandable behavior
+is used by default. (Although I sometimes go back and forth on switching
+it.)
+"""]]