{"thread":{"id":"3622","subject":"proxy documentation","startedAt":"2006-03-11T00:49:14Z","lastAt":"2006-03-11T00:49:14Z","messageCount":1,"participants":["Tony Luck"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"17443","messageId":"12c511ca0603101649y51311f0du1a165596428b31b3@mail.gmail.com","threadId":"3622","inReplyTo":null,"subject":"proxy documentation","fromName":"Tony Luck","fromEmail":"tony.luck@intel.com","sentAt":"2006-03-11T00:49:14Z","receivedAt":"2006-03-11T00:49:14Z","isPatch":false,"sender":{"key":"tony.luck@intel.com","avatar":"https://avatars.githubusercontent.com/u/5446021?v=4"},"body":"Example documentation for proxy settings in Documentation/git-repo-config.txt\nshows:\n\n[proxy]\n                command=\"ssh\" for \"ssh://kernel.org/\"\n\nBut the code in connect.c:git_proxy_command_options() looks\nfor \"core.gitproxy\" rather than \"proxy.command\".\n\nI've only just started looking at the proxy support ... is it just the name\nthat is wrong in the documentation, or are there other issues here?\n\nproxy.command sounds like a better name than core.gitproxy ... so\nmaybe the Docs are \"right\" and the code is \"wrong\"?\n\n-Tony\n"}]}