{"thread":{"id":"9374","subject":"[PATCH] Document GIT_SSH environment variable alongside other variables","startedAt":"2007-08-04T06:06:52Z","lastAt":"2007-08-05T22:16:40Z","messageCount":2,"participants":["Shawn O. Pearce","Jakub Narebski"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"49669","messageId":"20070804060652.GA28379@spearce.org","threadId":"9374","inReplyTo":null,"subject":"[PATCH] Document GIT_SSH environment variable alongside other variables","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-08-04T06:06:52Z","receivedAt":"2007-08-04T06:06:52Z","isPatch":true,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"The GIT_SSH environment variable has survived for quite a while\nwithout being documented, but has been mentioned on list and on\nmy day-job repositories can only be accessed via magic supplied\nthrough the wonderous hack that is GIT_SSH.\n\nAdvertising it alongside other \"low level magic\" such as GIT_PAGER\nand GIT_MERGE_VERBOSITY will certainly help others who need to\nspread their own pixie dust to make things work.\n\nSigned-off-by: Shawn O. Pearce <spearce@spearce.org>\n---\n Documentation/git.txt |   16 ++++++++++++++++\n 1 files changed, 16 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/git.txt b/Documentation/git.txt\nindex 4c4d174..18f8b6a 100644\n--- a/Documentation/git.txt\n+++ b/Documentation/git.txt\n@@ -421,6 +421,22 @@ other\n \tto an empty string or to the value \"cat\", git will not launch\n \ta pager.\n \n+'GIT_SSH'::\n+\tIf this environment variable is set then gitlink:git-fetch[1]\n+\tand gitlink:git-push[1] will use this command instead\n+\tof `ssh` when they need to connect to a remote system.\n+\tThe 'GIT_SSH' command will be given exactly two arguments:\n+\tthe 'username@host' (or just 'host') from the URL and the\n+\tshell command to execute on that remote system.\n++\n+To pass options to the program that you want to list in GIT_SSH\n+you will need to wrap the program and options into a shell script,\n+then set GIT_SSH to refer to the shell script.\n++\n+Usually it is easier to configure any desired options through your\n+personal `.ssh/config` file.  Please consult your ssh documentation\n+for further details.\n+\n 'GIT_FLUSH'::\n \tIf this environment variable is set to \"1\", then commands such\n \tas git-blame (in incremental mode), git-rev-list, git-log,\n-- \n1.5.3.rc3.941.gaac97\n"},{"id":"49953","messageId":"200708060016.40829.jnareb@gmail.com","threadId":"9374","inReplyTo":"20070804060652.GA28379@spearce.org","subject":"Re: [PATCH] Document GIT_SSH environment variable alongside other variables","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2007-08-05T22:16:40Z","receivedAt":"2007-08-05T22:16:40Z","isPatch":true,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Shawn O. Pearce wrote:\n\n> The GIT_SSH environment variable has survived for quite a while\n> without being documented, but has been mentioned on list and on\n> my day-job repositories can only be accessed via magic supplied\n> through the wonderous hack that is GIT_SSH.\n\nThanks a lot.\n\nBy the way, I plan on documenting existing environmental variables used \nby git better (for after 1.5.3). First, separate \"Environmental \nvariables\" section in Documentation/git.txt into separate file (similar \nto the config.txt file), named environment.txt. Second, add to the list \nof variables links to variables which are documented in other manpages, \nsimilarly to how for example GIT_AUTHOR_NAME etc. are described. Then \nadd one by one environmental variables which are not documented at all: \nGIT_SSH_PUSH/GIT_SSH_PULL, GIT_CURL_VERBOSITY, GIT_REFLOG_ACTION, \nGIT_GRAFT_FILE and GIT_TEMPLATE_DIR.\n\n-- \nJakub Narebski\nPoland\n"}]}