From 11e4c583c75bb83d71e447993034b6404939c961 Mon Sep 17 00:00:00 2001 From: NhanHo Date: Tue, 24 May 2016 10:39:34 +0000 Subject: --- doc/bugs/gcrypt_special_remote_not_being_encrypted.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/bugs/gcrypt_special_remote_not_being_encrypted.mdwn b/doc/bugs/gcrypt_special_remote_not_being_encrypted.mdwn index 6b4c8daac..3d4a21762 100644 --- a/doc/bugs/gcrypt_special_remote_not_being_encrypted.mdwn +++ b/doc/bugs/gcrypt_special_remote_not_being_encrypted.mdwn @@ -38,7 +38,7 @@ 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 content). When using gcrypt special remote on local machine , it does not seem to be an issue. -- cgit v1.2.3