summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar NhanHo <NhanHo@web>2016-05-24 09:08:35 +0000
committerGravatar admin <admin@branchable.com>2016-05-24 09:08:35 +0000
commit004863c519a8a549425977685da2c5f2fc5679fe (patch)
tree5e769be6b6b811fe6a64b462cefe09e52e8e0c5a
parentcc5e7673cf236357a9c7e7f07af8cf51d046fd86 (diff)
-rw-r--r--doc/bugs/gcrypt_special_remote_not_being_encrypted.mdwn4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/bugs/gcrypt_special_remote_not_being_encrypted.mdwn b/doc/bugs/gcrypt_special_remote_not_being_encrypted.mdwn
index 0650bc6c8..6b4c8daac 100644
--- a/doc/bugs/gcrypt_special_remote_not_being_encrypted.mdwn
+++ b/doc/bugs/gcrypt_special_remote_not_being_encrypted.mdwn
@@ -38,7 +38,9 @@ grep -r "Banana" . #On the other hand, this has a result
> ./annex/objects/ee1/042/SHA256E-s5--11861eaa2e70e8ac73d9d20cd172b6a5396cb0116fed5bfe432ca075144b2d48.org/SHA256E-s5--11861eaa2e70e8ac73d9d20cd172b6a5396cb0116fed5bfe432ca075144b2d48.org:BananaTest
```
-If the first machine do `git annex sync --content`, it can get and view the new file normally, trying to add new file afterward from the first machine works fine as well. Adding file from the 2nd machine results in the same behaviour (unencrypted file name)
+If the first machine do `git annex sync --content`, it can get and view the new file normally, trying to add new file afterward from the first machine works fine as well. Adding file from the 2nd machine results in the same behaviour (unencrypted file name).
+
+When using gcrypt special remote on local machine , it does not seem to be an issue.
### What version of git-annex are you using? On what operating system?