It does seem that adding an extra check during a Windows/case-insensitive
checkout for 'duplicate' filemames would be a useful addition.
P.
----- Original Message -----
From: joeriel...@gmail.com
To: git-users@googlegroups.com
Sent: Saturday, December 21, 2013 9:52 PM
Subject: [git-users] Re: git clone on windows creates modified file
The problem came about because I had two files with names that different only
by case
(one was Debugger.mm, the other debugger.mm). Windows file system is case
insensitive,
so that causes a collision when cloning. The solution was to rename one of
the files.
On Friday, December 20, 2013 9:07:47 AM UTC-8, joeri...@gmail.com wrote:
I normally use git on linux, though I have an installation on a Windows 7
laptop.
When using it yesterday to clone a repository on my linux machine, the clone
would open with one of the files modified. I could not undo the
modification.
Repeated cloning would do the same thing. I then tried cloning from the
original
repo, but using a linux partition on that laptop. It worked fine. Any
idea why the
Windows git doesn't work?
--
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 to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
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
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
