diff options
| author |  zedr0nre@e1b86776f21c5f6a6e064c6ab8da039b54915b7d <zedr0nre@web> | 2015-08-03 23:15:39 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2015-08-03 23:15:39 +0000 |
| commit | 49386944333cc486127bcee7da632b3d9418e6b3 (patch) | |
| tree | 8fa0e8b0fbe9c092edad7eaff98c663aca05550c | |
| parent | 78b22a7720fa93dff4db18a88763c052dc8df0f9 (diff) | |
Added a comment
| -rw-r--r-- | doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_10_a231fdd39c48184acfa7a9a825035400._comment | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_10_a231fdd39c48184acfa7a9a825035400._comment b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_10_a231fdd39c48184acfa7a9a825035400._comment new file mode 100644 index 000000000..6649169dc --- /dev/null +++ b/doc/bugs/git-annex_sync_under_windows_fails_by_using_itself_as_the_ssh_command/comment_10_a231fdd39c48184acfa7a9a825035400._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="zedr0nre@e1b86776f21c5f6a6e064c6ab8da039b54915b7d" + nickname="zedr0nre" + subject="comment 10" + date="2015-08-03T23:15:39Z" + content=""" +Here's a workaround i found for now - inspired by [http://superuser.com/questions/232373/how-to-tell-git-which-private-key-to-use](http://superuser.com/questions/232373/how-to-tell-git-which-private-key-to-use) + +so when cloning from ssh before syncing use + +`git clone 'ext:ssh server.com %S /path/to/repository.git ' ` + +instead of + +`git clone ssh://server.com/path/to/repository.git` + +That allows git annex sync to work for me +"""]] |