From 6584d875d639663d433a1031d066d64880918248 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 13 Dec 2016 12:53:12 -0400 Subject: [PATCH] response --- ...nt_2_7b3f5d2e9de4b13de821177db2f57bcd._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/forum/more_intelligent_copy_/comment_2_7b3f5d2e9de4b13de821177db2f57bcd._comment 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 0000000000..474a068b65 --- /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.) +"""]]