{"thread":{"id":"22453","subject":"FEATURE REQUEST: Allow SSH style URLS (with extra colon)","startedAt":"2010-01-30T16:57:56Z","lastAt":"2010-01-30T22:30:04Z","messageCount":4,"participants":["Jari Aalto","Ilari Liusvaara","Petr Baudis","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"133124","messageId":"87tyu3cyy3.fsf@jondo.cante.net","threadId":"22453","inReplyTo":null,"subject":"FEATURE REQUEST: Allow SSH style URLS (with extra colon)","fromName":"Jari Aalto","fromEmail":"jari.aalto@cante.net","sentAt":"2010-01-30T16:57:56Z","receivedAt":"2010-01-30T16:57:56Z","isPatch":false,"sender":{"key":"jari.aalto@cante.net","avatar":"https://avatars.githubusercontent.com/u/34601?v=4"},"body":"\nAccording to git-clone[1] the SSH protocol is specied as:\n\n    ssh://[user@]host.xz[:port]/path\n\nIt woudl be nice if the \":\" were allowed, so that the familiar SSH style\npatch notation could be used, making the spec:\n\n    ssh://[user@]host.xz[:[port]]/path\n\nAn example:\n\n    ssh://foo@examplecom:/path\n                        |\n                        Allowed\n\nJari\n\n[1] http://www.kernel.org/pub/software/scm/git/docs/git-clone.html\n"},{"id":"133126","messageId":"20100130172730.GA28865@Knoppix","threadId":"22453","inReplyTo":"87tyu3cyy3.fsf@jondo.cante.net","subject":"Re: FEATURE REQUEST: Allow SSH style URLS (with extra colon)","fromName":"Ilari Liusvaara","fromEmail":"ilari.liusvaara@elisanet.fi","sentAt":"2010-01-30T17:27:30Z","receivedAt":"2010-01-30T17:27:30Z","isPatch":false,"sender":{"key":"ilari.liusvaara@elisanet.fi","avatar":null},"body":"On Sat, Jan 30, 2010 at 06:57:56PM +0200, Jari Aalto wrote:\n> \n> According to git-clone[1] the SSH protocol is specied as:\n> \n>     ssh://[user@]host.xz[:port]/path\n> \n> It woudl be nice if the \":\" were allowed, so that the familiar SSH style\n> patch notation could be used, making the spec:\n> \n>     ssh://[user@]host.xz[:[port]]/path\n> \n> An example:\n> \n>     ssh://foo@examplecom:/path\n>                         |\n>                         Allowed\n> \n\nI would use:\n\nssh://[user@]host.xz[:port][:]/path\n\nSince empty port isn't allowed, this grammar is uniquely parseable,\nand would allow specifying port too (if you don't need to specify\nit, you could just use the scp syntax)[1].\n\n[1] Of course 'ssh://[user@]host.xz[:port]/~/path' works too..\n\n-Ilari\n"},{"id":"133141","messageId":"20100130222157.GI9553@machine.or.cz","threadId":"22453","inReplyTo":"87tyu3cyy3.fsf@jondo.cante.net","subject":"Re: FEATURE REQUEST: Allow SSH style URLS (with extra colon)","fromName":"Petr Baudis","fromEmail":"pasky@suse.cz","sentAt":"2010-01-30T22:21:57Z","receivedAt":"2010-01-30T22:21:57Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"On Sat, Jan 30, 2010 at 06:57:56PM +0200, Jari Aalto wrote:\n> \n> According to git-clone[1] the SSH protocol is specied as:\n> \n>     ssh://[user@]host.xz[:port]/path\n> \n> It woudl be nice if the \":\" were allowed, so that the familiar SSH style\n> patch notation could be used, making the spec:\n> \n>     ssh://[user@]host.xz[:[port]]/path\n> \n> An example:\n> \n>     ssh://foo@examplecom:/path\n>                         |\n>                         Allowed\n\nBut that's not an URL anymore. If you want to use ssh pathspec, write it\nas a pathspec, not an URL. Just foo@example.com:/path works fine. ;-)\n\n\t\t\t\tPetr \"Pasky\" Baudis\n"},{"id":"133143","messageId":"7v4om3jker.fsf@alter.siamese.dyndns.org","threadId":"22453","inReplyTo":"20100130222157.GI9553@machine.or.cz","subject":"Re: FEATURE REQUEST: Allow SSH style URLS (with extra colon)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2010-01-30T22:30:04Z","receivedAt":"2010-01-30T22:30:04Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Petr Baudis <pasky@suse.cz> writes:\n\n> On Sat, Jan 30, 2010 at 06:57:56PM +0200, Jari Aalto wrote:\n>> \n>> An example:\n>> \n>>     ssh://foo@examplecom:/path\n>>                         |\n>>                         Allowed\n>\n> But that's not an URL anymore. If you want to use ssh pathspec, write it\n> as a pathspec, not an URL. Just foo@example.com:/path works fine. ;-)\n\nThe way URLs are defined is:\n\n\t<scheme>:<scheme-specific-part>\n\nso if somebody defines his \"ssh\" scheme to allow any random garbage, its\ntheir URL and you cannot say \"that is not an URL\", unless you qualify your\nstatement with \"I want to keep ssh scheme consistent with the common\ninternet scheme syntax\".\n\nAs I think \"ssh://...\" is simply moronic, I don't even care to \"keep\" the\nscheme specific part consistent with the common internet scheme syntax to\nbegin with.  I agree with your conclusion, though ;-)\n\nscp syntax works just fine.\n"}]}