summaryrefslogtreecommitdiff
path: root/hex.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2017-01-25 14:35:36 -0800
committerJunio C Hamano <gitster@pobox.com>2017-01-25 15:05:08 -0800
commitaabadcf65291d16ecf7897ed2a26269ddb3f83d2 (patch)
tree868be7c9c840c5a50649986ca4ff0bbdaaf47329 /hex.c
parent1b1720a1399a7ab78aeb135922e90d086adf9f13 (diff)
downloadgit-sf/putty-plink-in-ssh-command.tar.gz
connect: core.sshvariant to correct misidentificationsf/putty-plink-in-ssh-command
While the logic we have been using to guess which variant of SSH implementation is in use by looking at the name of the program has been robust enough for GIT_SSH (which does not go through the shell, hence it can only spell the name the SSH program and nothing else), extending it to GIT_SSH_COMMAND and core.sshcommand opens it for larger chance of misidentification, because these can specify arbitrary shell command, and a simple "the first word on the line must be the command name" heuristic may not even look at the command name at all. As any effort to improve the heuristic will give us only diminishing returns, and especially given that most of the users are expected to have a command line for which the heuristic would work correctly, give an explicit escape hatch to override a misidentification, just in case one happens. It is arguably bad to add this new variable to the core.* set, in the sense that you'll never see this variable if you do not interact with other repositories over ssh, but core.sshcommand is already there for some reason, so let's match it. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'hex.c')
0 files changed, 0 insertions, 0 deletions