From 57a0929a61e7540e2c416e597a4e941e881e5ea2 Mon Sep 17 00:00:00 2001 From: "http://olivier.berger.myopenid.com/" Date: Fri, 23 Aug 2013 19:59:35 +0000 Subject: [PATCH] Added a comment: Git annex copy needed before git annex sync --- ...omment_14_ff4ffc2aabc5fd174d7386ef13860f78._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/direct_mode/comment_14_ff4ffc2aabc5fd174d7386ef13860f78._comment diff --git a/doc/direct_mode/comment_14_ff4ffc2aabc5fd174d7386ef13860f78._comment b/doc/direct_mode/comment_14_ff4ffc2aabc5fd174d7386ef13860f78._comment new file mode 100644 index 0000000000..3a538e00b3 --- /dev/null +++ b/doc/direct_mode/comment_14_ff4ffc2aabc5fd174d7386ef13860f78._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://olivier.berger.myopenid.com/" + nickname="obergix" + subject="Git annex copy needed before git annex sync" + date="2013-08-23T19:59:35Z" + content=""" +Thanks for these details @joeyh. But AFAIU, one needs to proceed to the git annex copy before doing the git annex sync, otherwise, symlinks (or files containing the symlink path on SMB) will be created, instead of the plain \"direct\" files that are expected. + +I'm still not sure whether the git annex sync needs to be issued on either of the indirect or direct remotes first, or both, then in which sequence. I think a \"walkthrough\" script would help. +"""]]