On Jan 22, 2008 10:52 AM, Reece Dunn <msclrhd@xxxxxxxxxxxxxx> wrote: > This is what I am saying. For example, if you say: > > git mv myfile.H myfile.h > > on a case sensitive filesystem (e.g. ext3), this will work, however on > a case insensitive filesystem (e.g. ntfs) git would complain that the > files are the same. > > The workaround is to say: > > git mv myfile.H myfile.h.tmp > git mv myfile.h.tmp myfile.h > > but this is not ideal, especially if you are automating some move operations. > If I remember correctly, this fails when it comes to applying the commit containing that move, at least on HFS+. You could create 2 commits (one with the first mv, one with the second), and apply them one at a time, but it's a pretty unpleasant workaround. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
