mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2017-03-21 13:43:10 -04:00
parent e398a9854c
commit e183270393
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
1 changed files with 18 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
doc/bugs/cannot___40__or_how__63____41___to_pass_socket_path_with_a_space_in_its_path_via_annex-ssh-options/comment_1_d773dee03276e9b0e0b75d0709b76278._comment Normal file
View file

@ -0,0 +1,18 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2017-03-21T17:38:57Z"
content="""
You can't accomplish this with `remote.<name>.annex-ssh-options`,
since it is not exposed to the shell, and the parser just breaks it up into
words.
A smarter parser would be needed. Or you could configure it in
~/.ssh/config, or perhaps make a ssh config file elsewhere and use
annex-ssh-options to pass -F to ssh to make it use this other config file.
Now that git-annex supports `GIT_SSH_COMMAND`, which is exposed to the
shell, you should be able to accomplish it that way. I don't know if that
would work in your use case, since the environment variable affects all ssh
remotes, not just one.
"""]]