git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Kevin Daudt <me@ikke.info>
To: "Bonk, Gregory" <gbonk@icct.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: FW: Issue in gitbash changing directory
Date: Tue, 18 Apr 2017 18:53:30 +0200	[thread overview]
Message-ID: <20170418165330.GB24697@alpha.ikke.info> (raw)
In-Reply-To: <DM5PR04MB061992BA437ACAD18A5F44DBC7190@DM5PR04MB0619.namprd04.prod.outlook.com>

On Tue, Apr 18, 2017 at 12:48:09PM +0000, Bonk, Gregory wrote:
> 
> I accidently typed 'cd //'  and it worked.
> 
> gbonk@ICC11167 MINGW64 /c/git/mtb-messagehub-information-radiator (master)
> $ cd //
> 
> gbonk@ICC11167 MINGW64 //
> $ cd ..

This has very little to do with git, but more with bash (the shell that
is interpretting the command. From a bash FAQ [1]:

> E10) Why does `cd //' leave $PWD as `//'?
> 
> POSIX.2, in its description of `cd', says that *three* or more leading
> slashes may be replaced with a single slash when canonicalizing the
> current working directory.
> 
> This is, I presume, for historical compatibility.  Certain versions of
> Unix, and early network file systems, used paths of the form
> //hostname/path to access `path' on server `hostname'.

So this is kind of intentional.


[1]: https://tiswww.case.edu/php/chet/bash/FAQ

      reply	other threads:[~2017-04-18 17:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DM5PR04MB061907F6F650E56FE2ECBCD5C7190@DM5PR04MB0619.namprd04.prod.outlook.com>
     [not found] ` <DM5PR04MB06197EF8FA0344708A69C842C7190@DM5PR04MB0619.namprd04.prod.outlook.com>
2017-04-18 12:48   ` FW: Issue in gitbash changing directory Bonk, Gregory
2017-04-18 16:53     ` Kevin Daudt [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170418165330.GB24697@alpha.ikke.info \
    --to=me@ikke.info \
    --cc=gbonk@icct.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).