Please describe the problem.
Instead of storing config for each remote in ~/.ssh/config, which mixes the user own config with that of git-annex-assistant, which is irritating if (like me) you store your ssh config in a vcs. Since the option -F allows the choice of the config file, it should be possible to move the config into ~/.ssh/git-annex/config. The only issue I see is according to the ssh man page on my system states that the system-wide config is ignored if a config file is specified on the command line.
What version of git-annex are you using? On what operating system?
I'm using git-annex 4.20130601 on a Debian Testing/Unstable/Experimental mix.
?wontfix
The only interface git provides to do this is
GIT_SSH, which would have to be set to a wrapper script that runs ssh with the desirned options.And if that were used,
git pullby itself would not work on the repositories set up by the assistant. I don't consider that very nice.Also, if you're going to set up something like local pairing, why would you not want to commit that config to git along with your other ssh configs? Config files in $HOME are quite frequently edited by helper programs to configure changes, and I personally commit those changes all the time.
Perhaps your real problem is that you have one
.ssh/configthat is shared between multiple hosts, and the git-annex settings are specific to a single host. Have you considered using vcsh?If it were sane, I'd probably use it.
In the meantime, I'm moving this to todo.