git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ricky Clarkson <ricky.clarkson@gmail.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: git@vger.kernel.org
Subject: Re: Case sensitivity on Windows for absolute paths.
Date: Sun, 25 Apr 2010 19:47:23 +0100	[thread overview]
Message-ID: <r2z7eeb06461004251147jce635231kca659b52a48571d0@mail.gmail.com> (raw)
In-Reply-To: <201004252008.27823.j6t@kdbg.org>

Hi Johannes,

$ cd /c/uk-org-netvu/

Ricky@RICKY-XP /c/uk-org-netvu (trunk)
$ cmd
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

c:\uk-org-netvu>

If I run cmd via Start -> Run, then the prompt shows C:\uk-org-netvu>

I also verified this using the Scala interpreter, printing out
System.getProperty("user.dir"), which varied similarly in case
depending on whether I started it from cmd or from Git Bash.

Thanks,
Ricky.

--
Ricky Clarkson
Java and Scala Programmer, AD Holdings
+44 1928 706373
Skype: ricky_clarkson
Google Talk: ricky.clarkson@gmail.com
Google Wave: ricky.clarkson@googlewave.com



On 25 April 2010 19:08, Johannes Sixt <j6t@kdbg.org> wrote:
> On Sonntag, 25. April 2010, Ricky Clarkson wrote:
>> It would be good if git automatically uppercased the drive letter,
>> yes.  However, I found the real root of my problem.  Git Bash
>> (msysgit) sets the working directory to c:\foo for programs launched
>> if the working directory within it is /c/foo.
>
> I don't understand what you mean. Git Bash cannot influence whether git sees
> the drive letter in the working directory in uppercase or lowercase. Unless
> by "working directory" you mean something else than what getcwd() returns.
>
> -- Hannes
>

      reply	other threads:[~2010-04-25 18:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23 14:12 Case sensitivity on Windows for absolute paths Ricky Clarkson
2010-04-23 19:46 ` Johannes Sixt
2010-04-25  7:33   ` Ricky Clarkson
2010-04-25 18:08     ` Johannes Sixt
2010-04-25 18:47       ` Ricky Clarkson [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

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

  git send-email \
    --in-reply-to=r2z7eeb06461004251147jce635231kca659b52a48571d0@mail.gmail.com \
    --to=ricky.clarkson@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=j6t@kdbg.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.
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 NNTP newsgroup(s).