{"thread":{"id":"45728","subject":"FW: Issue in gitbash changing directory","startedAt":"2017-04-18T12:48:15Z","lastAt":"2017-04-18T17:03:41Z","messageCount":2,"participants":["Bonk, Gregory","Kevin Daudt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"317103","messageId":"DM5PR04MB061992BA437ACAD18A5F44DBC7190@DM5PR04MB0619.namprd04.prod.outlook.com","threadId":"45728","inReplyTo":"DM5PR04MB06197EF8FA0344708A69C842C7190@DM5PR04MB0619.namprd04.prod.outlook.com","subject":"FW: Issue in gitbash changing directory","fromName":"Bonk, Gregory","fromEmail":"gbonk@icct.com","sentAt":"2017-04-18T12:48:09Z","receivedAt":"2017-04-18T12:48:15Z","isPatch":false,"sender":{"key":"gbonk@icct.com","avatar":null},"body":"\nI accidently typed 'cd //'  and it worked.\n\ngbonk@ICC11167 MINGW64 /c/git/mtb-messagehub-information-radiator (master)\n$ cd //\n\ngbonk@ICC11167 MINGW64 //\n$ cd ..\n\n\n"},{"id":"317117","messageId":"20170418165330.GB24697@alpha.ikke.info","threadId":"45728","inReplyTo":"DM5PR04MB061992BA437ACAD18A5F44DBC7190@DM5PR04MB0619.namprd04.prod.outlook.com","subject":"Re: FW: Issue in gitbash changing directory","fromName":"Kevin Daudt","fromEmail":"me@ikke.info","sentAt":"2017-04-18T16:53:30Z","receivedAt":"2017-04-18T17:03:41Z","isPatch":false,"sender":{"key":"me@ikke.info","avatar":"https://avatars.githubusercontent.com/u/135698?v=4"},"body":"On Tue, Apr 18, 2017 at 12:48:09PM +0000, Bonk, Gregory wrote:\n> \n> I accidently typed 'cd //'  and it worked.\n> \n> gbonk@ICC11167 MINGW64 /c/git/mtb-messagehub-information-radiator (master)\n> $ cd //\n> \n> gbonk@ICC11167 MINGW64 //\n> $ cd ..\n\nThis has very little to do with git, but more with bash (the shell that\nis interpretting the command. From a bash FAQ [1]:\n\n> E10) Why does `cd //' leave $PWD as `//'?\n> \n> POSIX.2, in its description of `cd', says that *three* or more leading\n> slashes may be replaced with a single slash when canonicalizing the\n> current working directory.\n> \n> This is, I presume, for historical compatibility.  Certain versions of\n> Unix, and early network file systems, used paths of the form\n> //hostname/path to access `path' on server `hostname'.\n\nSo this is kind of intentional.\n\n\n[1]: https://tiswww.case.edu/php/chet/bash/FAQ\n"}]}