From 3ee526a3a61a0d9bb4bc702b220716a29e72cd26 Mon Sep 17 00:00:00 2001 From: "fasthans@87884c78197fe1a25ac25ae7fa1d930c147e9592" Date: Tue, 15 Oct 2019 13:28:14 +0000 Subject: [PATCH] --- .../unable_to_access_remotes_when_cloning_a_gcrypt_remote.mdwn | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/forum/unable_to_access_remotes_when_cloning_a_gcrypt_remote.mdwn b/doc/forum/unable_to_access_remotes_when_cloning_a_gcrypt_remote.mdwn index 978215d486..e6936e9e7b 100644 --- a/doc/forum/unable_to_access_remotes_when_cloning_a_gcrypt_remote.mdwn +++ b/doc/forum/unable_to_access_remotes_when_cloning_a_gcrypt_remote.mdwn @@ -4,9 +4,11 @@ On my old computer, I was using a removable hard drive with a bare repo as my re I follow the relevant steps exactly: +``` git clone gcrypt::/media/me/path_to_repo clone cd clone git annex enableremote path_to_repo gitrepo=/media/me/path_to_repo +``` Now `git annex sync` reports success for both `origin` and `path_to_repo`. But `git annex sync --content` fails with: