git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ricky Clarkson <ricky.clarkson@gmail.com>
To: git@vger.kernel.org
Subject: Case sensitivity on Windows for absolute paths.
Date: Fri, 23 Apr 2010 15:12:26 +0100	[thread overview]
Message-ID: <o2v7eeb06461004230712i2c8c1e61l4c50a73a4f6c83d@mail.gmail.com> (raw)

Hi,

I noticed that if I have a git repository at C:\foo, and there is a
file in there named bar, git add bar works fine, git add C:\foo/bar
works fine but git add c:\foo/bar does not.  git reports that the file
'is outside repository'.  Looking at setup.c it seems that string
comparisons are being used to determine whether a file is within the
repository.

For my purposes I can probably make a Windows build that does it while
ignoring the case, but is there a more proper way that git should do
it?  I'm not familiar enough with the POSIX file routines to know.

A separate tool, maven, is what specifies it as lowercase, otherwise I
would obviously just write C: instead of c: myself.  I think I know
how to fix that so it uses relative paths, and will look into that,
but it would be good to have git do the right thing too.

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

             reply	other threads:[~2010-04-23 14:12 UTC|newest]

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

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=o2v7eeb06461004230712i2c8c1e61l4c50a73a4f6c83d@mail.gmail.com \
    --to=ricky.clarkson@gmail.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.
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).