faecd73f32
They are handled close the same as they are by git. However, unlike git, git-annex sometimes needs to pass the -n parameter when using these. So, this has the potential for breaking some setup, and perhaps there ought to be a ANNEX_USE_GIT_SSH=1 needed to use these. But I'd rather avoid that if possible, so let's see if anyone complains. Almost all places where "ssh" was run have been changed to support the env vars. Anything still calling sshOptions does not support them. In particular, rsync special remotes don't. Seems that annex-rsync-transport already gives sufficient control there. (Fixed in passing: Remote.Helper.Ssh.toRepo used to extract remoteAnnexSshOptions and pass them to sshOptions, which was redundant since sshOptions also extracts those.) This commit was sponsored by Jeff Goeke-Smith on Patreon. |
||
|---|---|---|
| .. | ||
| Chunked | ||
| AWS.hs | ||
| Chunked.hs | ||
| Encryptable.hs | ||
| Git.hs | ||
| Hooks.hs | ||
| Http.hs | ||
| Messages.hs | ||
| ReadOnly.hs | ||
| Special.hs | ||
| Ssh.hs | ||