From 724c004b221d95f4832628e3487047ee6240ca1f Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 12 Oct 2015 14:55:02 -0400 Subject: [PATCH] response --- ..._1_5a8e599d6e22e7c1960bd1715666657b._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/bugs/SSL_repos_does_not_show_up_in_Assistant/comment_1_5a8e599d6e22e7c1960bd1715666657b._comment diff --git a/doc/bugs/SSL_repos_does_not_show_up_in_Assistant/comment_1_5a8e599d6e22e7c1960bd1715666657b._comment b/doc/bugs/SSL_repos_does_not_show_up_in_Assistant/comment_1_5a8e599d6e22e7c1960bd1715666657b._comment new file mode 100644 index 0000000000..d394ca039d --- /dev/null +++ b/doc/bugs/SSL_repos_does_not_show_up_in_Assistant/comment_1_5a8e599d6e22e7c1960bd1715666657b._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-10-12T18:52:42Z" + content=""" +You seem to be talking about using https to access a git repository. + +git-annex is not generally able to use https as a transport -- ie, it +can maybe download files from a git repository over https, if +the repository is set up just right. But it can't upload file to that +repository, nor can it promptly notice when changes are synced to that +repository from elsewhere. + +So, there's not much that the assistant can do with such a repository. + +You'll be better off using ssh for your git-annex repositories. +"""]]