On Sun, 19 Apr 2015 15:04:26 -0700 (PDT)
Thomas Ferris Nicolaisen <tfn...@gmail.com> wrote:
> > Hi, I am unable to reset my working copy changes.
> > I have two files in this project which differ only in their case:
> > listwise/liblistwise/op/c/c.c
> > listwise/lblistwise/op/C/C.c
> > It appears that git is being confused by the similar file names.
> > Is this a bug?
> > todd@HOSSBEAST /q/Code/fab (master)
> > $ git version
> > git version 1.9.5.msysgit.1
> I'm assuming you're on Windows since you use a Git built with
> Windows does not have a case-sensitive file-system.
Nit-picking a bit, NTFS is case-preserving but case-insensitive.
That is, given the right tools, it is actually possible to rename "foo"
to "fOO", and the name will be stored as "fOO" (no case conversion is
done). But yes, when matching a file name against the entries
of the directory it's located in, NTFS performs case-insensitive
AFAIK, HFS on Mac OS X exhibits the same behaviour.
> If you are in control of this repository, I would heavily recommend
> changing some naming conventions. Having multiple files with the same
> name is asking for trouble and confusion.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.