aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawnjjCyhVEcTRM5m4iIBqL3ZCooPx7ZYB_E <Marcus@web>2013-01-07 11:35:00 +0000
committerGravatar admin <admin@branchable.com>2013-01-07 11:35:00 +0000
commited8cc587eadafadac10f919a9fb4b9f183bf50b7 (patch)
tree983547dc6964a361c67d84d8e21eb08f1a5bde89
parent270acb6dca4324a17a9cf4391b487c23b39190ba (diff)
-rw-r--r--doc/bugs/renaming_a_file_makes_annex_get_the_file__39__s_content_from_remote.mdwn25
1 files changed, 25 insertions, 0 deletions
diff --git a/doc/bugs/renaming_a_file_makes_annex_get_the_file__39__s_content_from_remote.mdwn b/doc/bugs/renaming_a_file_makes_annex_get_the_file__39__s_content_from_remote.mdwn
new file mode 100644
index 000000000..f7365d098
--- /dev/null
+++ b/doc/bugs/renaming_a_file_makes_annex_get_the_file__39__s_content_from_remote.mdwn
@@ -0,0 +1,25 @@
+# What steps will reproduce the problem?
+
+1. Use assistant to setup a local repository (client group) and a remote repository (via ssh, backup group).
+
+2. Add some big files and wait for them to be syncronized.
+
+3. Manually switch to indirect mode (to make 'drop' work)
+
+4. Drop the file's content from the local repository.
+
+5. Rename the file using any file manager or mv on the command line.
+
+
+# What is the expected output? What do you see instead?
+
+* Expected outcome was the file being renamed and that name change being propagated to the remote repository without re-transferring the whole file. I didn't drop it for nothing!
+
+* Instead, the file was renamed and the file's content was retrieved from the remote repository.
+
+
+# What version of git-annex are you using? On what operating system?
+
+Git-Annex 3.20130102
+
+Arch Linux on x64.