From 842f8da6b7b0e8b4b8288c18cf879fc0fae84fbc Mon Sep 17 00:00:00 2001 From: "https://me.yahoo.com/a/EbvxpTI_xP9Aod7Mg4cwGhgjrCrdM5s-#7c0f4" Date: Thu, 2 Jun 2016 13:02:42 +0000 Subject: [PATCH] fixed typo and commented about replication --- ..._seems_to_cause_migration_of_a_file_to_another_backend.mdwn | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/bugs/git_annex_adjust_--unlock_seems_to_cause_migration_of_a_file_to_another_backend.mdwn b/doc/bugs/git_annex_adjust_--unlock_seems_to_cause_migration_of_a_file_to_another_backend.mdwn index 096f1fc70d..443a1abd2d 100644 --- a/doc/bugs/git_annex_adjust_--unlock_seems_to_cause_migration_of_a_file_to_another_backend.mdwn +++ b/doc/bugs/git_annex_adjust_--unlock_seems_to_cause_migration_of_a_file_to_another_backend.mdwn @@ -1,6 +1,7 @@ ### Please describe the problem. -Interestingly, on my first attempt I had two files which migrated from MD5 to MD5E backend, but may be I have done some steps differently which provoked also also utils/test/test_data.tar.gz to get to the same destine. I am a bit confused why git diff reports change in the symlink if file is already a real file (I guess all the smudging magic) +Interestingly, on my first attempt I had two files which migrated from MD5 to MD5E backend, but may be I have done some steps differently which provoked also also utils/test/test_data.tar.gz to get to the same destiny (actually later replicated on a fresh clone). +I am also a bit confused why git diff reports change in the symlink if file is already a real file (I guess all the smudging magic) ### Please provide any additional information below.