From cf08c304610f8e4ca91c4cd9c768ab0e9471a881 Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Thu, 19 Sep 2019 19:09:31 +0000 Subject: [PATCH] added an issue where commands on unlocked, changed file use its old key --- .../commands_on_unlocked__44___changed_file_use_its_old_key.mdwn | 1 + 1 file changed, 1 insertion(+) create mode 100644 doc/bugs/commands_on_unlocked__44___changed_file_use_its_old_key.mdwn diff --git a/doc/bugs/commands_on_unlocked__44___changed_file_use_its_old_key.mdwn b/doc/bugs/commands_on_unlocked__44___changed_file_use_its_old_key.mdwn new file mode 100644 index 0000000000..91640791d7 --- /dev/null +++ b/doc/bugs/commands_on_unlocked__44___changed_file_use_its_old_key.mdwn @@ -0,0 +1 @@ +git-annex commands that take a file path as argument but really operate on the key corresponding to the file's contents, when given an unlocked file that has been modified, will operate on the original key, not the key corresponding to the file's current contents. For example, [[`git-annex-whereis`|git-annex-whereis]] can show that there are several copies of the contents, even though there is only one (and only in the working copy).