From 600829080f98afdd02f7e04b6b66f8387fc565ca Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 9 Jun 2017 13:50:59 -0400 Subject: comment --- .../comment_2_d1f803b68c3789854e483da1318d043d._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/forum/Shared_repository_without_git-annex_on_central_server/comment_2_d1f803b68c3789854e483da1318d043d._comment diff --git a/doc/forum/Shared_repository_without_git-annex_on_central_server/comment_2_d1f803b68c3789854e483da1318d043d._comment b/doc/forum/Shared_repository_without_git-annex_on_central_server/comment_2_d1f803b68c3789854e483da1318d043d._comment new file mode 100644 index 000000000..b8200fc48 --- /dev/null +++ b/doc/forum/Shared_repository_without_git-annex_on_central_server/comment_2_d1f803b68c3789854e483da1318d043d._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2017-06-09T17:47:45Z" + content=""" +The gcrypt special remote will work without git-annex being installed +on the server. The server only needs git and rsync. I think the +tip is fairly clear about that when it says + +"While this will work without git-annex being installed on the server, it +is recommended to have it installed." + +Without git-annex being available on the remote server, some things +like `git annex notifychanges` and content locking during dropping won't +work with that remote. The basics should work well enough to use it that +way. +"""]] -- cgit v1.2.3