{"thread":{"id":"4039","subject":"problem with plain git clone","startedAt":"2006-05-03T14:18:48Z","lastAt":"2006-05-03T15:46:18Z","messageCount":3,"participants":["Kumar Gala","Shawn Pearce"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"19430","messageId":"7CAB7A96-2C63-4B05-B0C6-72FC5B74D960@kernel.crashing.org","threadId":"4039","inReplyTo":null,"subject":"problem with plain git clone","fromName":"Kumar Gala","fromEmail":"galak@kernel.crashing.org","sentAt":"2006-05-03T14:18:48Z","receivedAt":"2006-05-03T14:18:48Z","isPatch":false,"sender":{"key":"galak@kernel.crashing.org","avatar":null},"body":"Anyone see an issues like the following:\n\n[kgala@kgala_lnx z]$ git clone git://git.kernel.org:/pub/scm/boot/u- \nboot/galak/u-boot.git\ngit clone git://git.kernel.org:/pub/scm/boot/u-boot/galak/u-boot.git\nfatal: unable to connect a socket (Connection timed out)\nfetch-pack from 'git://git.kernel.org:/pub/scm/boot/u-boot/galak/u- \nboot.git' failed.\n\nI've clearly done something crazy, but I setup this repository today  \nwith a simple:\n\ngit clone -n rsync://rsync.denx.de/git/u-boot.git\nmv u-boot/.git/ u-boot.git\n\n- kumar\n"},{"id":"19433","messageId":"20060503143130.GA9172@spearce.org","threadId":"4039","inReplyTo":"7CAB7A96-2C63-4B05-B0C6-72FC5B74D960@kernel.crashing.org","subject":"Re: problem with plain git clone","fromName":"Shawn Pearce","fromEmail":"spearce@spearce.org","sentAt":"2006-05-03T14:31:30Z","receivedAt":"2006-05-03T14:31:30Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Kumar Gala <galak@kernel.crashing.org> wrote:\n> Anyone see an issues like the following:\n> \n> [kgala@kgala_lnx z]$ git clone git://git.kernel.org:/pub/scm/boot/u- \n> boot/galak/u-boot.git\n> git clone git://git.kernel.org:/pub/scm/boot/u-boot/galak/u-boot.git\n> fatal: unable to connect a socket (Connection timed out)\n\nThere's no GIT daemon running on the empty port.  Notice the ':'\nappearing right after '.org'.\n\nHmm, that sounds like a bug in the protocol URL parser...\n\n-- \nShawn.\n"},{"id":"19441","messageId":"7814FB77-0073-40F3-BF1C-E2C7CEC7412D@kernel.crashing.org","threadId":"4039","inReplyTo":"20060503143130.GA9172@spearce.org","subject":"Re: problem with plain git clone","fromName":"Kumar Gala","fromEmail":"galak@kernel.crashing.org","sentAt":"2006-05-03T15:46:18Z","receivedAt":"2006-05-03T15:46:18Z","isPatch":false,"sender":{"key":"galak@kernel.crashing.org","avatar":null},"body":"\nOn May 3, 2006, at 9:31 AM, Shawn Pearce wrote:\n\n> Kumar Gala <galak@kernel.crashing.org> wrote:\n>> Anyone see an issues like the following:\n>>\n>> [kgala@kgala_lnx z]$ git clone git://git.kernel.org:/pub/scm/boot/u-\n>> boot/galak/u-boot.git\n>> git clone git://git.kernel.org:/pub/scm/boot/u-boot/galak/u-boot.git\n>> fatal: unable to connect a socket (Connection timed out)\n>\n> There's no GIT daemon running on the empty port.  Notice the ':'\n> appearing right after '.org'.\n>\n> Hmm, that sounds like a bug in the protocol URL parser...\n\nYeah, that was it. thanks.\n\n- kumar\n"}]}