{"thread":{"id":"2443","subject":"The host:remote syntax mess","startedAt":"2005-11-11T01:22:16Z","lastAt":"2005-11-11T01:46:20Z","messageCount":2,"participants":["Petr Baudis","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"11540","messageId":"20051111012216.GJ30496@pasky.or.cz","threadId":"2443","inReplyTo":null,"subject":"The host:remote syntax mess","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-11-11T01:22:16Z","receivedAt":"2005-11-11T01:22:16Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"  Hello,\n\n  I've just noticed that host:remote syntax seems to have been hijacked\nagain and is now attached to the GIT protocol in\n\n\tDocumentation/pull-fetch-param.txt\n\n(which BTW misses git+ssh). I said \"seems\", because connect.c still\nappears to assume it is SSH. So what is the plan? One possible\nexplanation is just that the git+ssh line should have been between the\ngit line and the : line in the documentation.\n\n  But if you really intend to change it, please don't. It's enough mess\nas it is now, and I'm actually not convinced at all that we should\nsupport it at all (god forbid promote it). When you have a location\nspecifier, you don't want it to randomly switch protocols, especially\nsuch significantly different ones as ssh and git.\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nVI has two modes: the one in which it beeps and the one in which\nit doesn't.\n"},{"id":"11542","messageId":"7vfyq4vtw3.fsf@assigned-by-dhcp.cox.net","threadId":"2443","inReplyTo":"20051111012216.GJ30496@pasky.or.cz","subject":"Re: The host:remote syntax mess","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-11-11T01:46:20Z","receivedAt":"2005-11-11T01:46:20Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Petr Baudis <pasky@ucw.cz> writes:\n\n>   I've just noticed that host:remote syntax seems to have been hijacked\n> again and is now attached to the GIT protocol in\n>\n> \tDocumentation/pull-fetch-param.txt\n>\n> (which BTW misses git+ssh). I said \"seems\", because connect.c still\n> appears to assume it is SSH. So what is the plan?\n\nSorry about that.  Thanks for noticing.\n\nThere is no plan to change that.  This documentation gotcha was\njust that yours truly stupidly merged documentation changes\nwithout reading every single line.\n\n-- >8 -- cut here -- >8 --\n[PATCH] Documentation: \"host:path/to/repo\" is git native over ssh.\n\nYou could also spell it ssh://host:/path/to/repo (or git+ssh,\nssh+git), but without method:// is shorter to type, so mention\nonly that one in the short and sweet list.\n\nSigned-off-by: Junio C Hamano <junkio@cox.net>\n---\ndiff --git a/Documentation/pull-fetch-param.txt b/Documentation/pull-fetch-param.txt\nindex 5c2888e..ddd5823 100644\n--- a/Documentation/pull-fetch-param.txt\n+++ b/Documentation/pull-fetch-param.txt\n@@ -8,7 +8,7 @@\n - Rsync URL:\t\trsync://remote.machine/path/to/repo.git/\n - HTTP(s) URL:\t\thttp://remote.machine/path/to/repo.git/\n - git URL:\t\tgit://remote.machine/path/to/repo.git/\n-\t\t\tor remote.machine:/path/to/repo.git/\n+- ssh URL:\t\tremote.machine:/path/to/repo.git/\n - Local directory:\t/path/to/repo.git/\n ===============================================================\n +\n"}]}