To verify that my issue was due to case-name insensitivity on Windows,
I renamed the file in the original repo, then cloned it. That worked
fine, there is now no modified file
On Saturday, December 21, 2013 1:35:36 PM UTC-8, joeri...@gmail.com wrote:
> In my case (I'm not the OP) the repository was created on a linux machine
> with 22.214.171.124. On the windows machine
> I've tried to clone it with cygwin git 1.7.4 and mysgit 1.8.4. Both show
> the same file as being modified, and diffing it
> shows significant differs.
> Oh. I think I know what's happening. The repo has two files, one named
> the other Debugger.mm. It is the Debugger.mm file that it thinks is
> modified and the diff is comparing it to debugger.mm.
> Is Windows not case sensitive? I think not.
> On Saturday, December 21, 2013 9:27:13 AM UTC-8, Philip Oakley wrote:
>> 1. Have you managed to reproduce this on any other repos?
>> 2. Is the repo, or a demonstrable fault variant, available publically?
>> 3. What does a diff of the current state with its last commit say (i.e.
>> what is the full detail hidden below the simple status)?
>> 4. Are yo at least able to share the filename/path of those failing files
>> (should it be related to that)?
>> 5. Does it have sub-modules ??
>> Are you able to try with a newer version 1.8.x to see if it's a fixed bug.
>> ----- Original Message -----
>> *From:* joeri...@gmail.com
>> *To:* git-...@googlegroups.com
>> *Sent:* Saturday, December 21, 2013 5:00 PM
>> *Subject:* [git-users] Re: Help, very strange behavior by Git
>> My post on a separate thread brings up what seems to be the same issue.
>> I'm seeing a modified file when I clone a git repository created on my
>> linux machine,
>> onto a Windows machine. I tried gc'ing the repo, setting core.autocrlf
>> to true on the
>> Windows machine, changing from cygwin git to msysgit, nothing helps.
>> Cloning to a linux machine does not show the modified file.
>> On Monday, June 7, 2010 4:01:42 PM UTC-7, Scott O wrote:
>>> I have a remote repository (at Assembla.com) for a virtual
>>> collaborative project. I'm using the version of git available via apt-
>>> get for ubuntu: 126.96.36.199. I have used Git for few months
>>> After the last commit, it now seems very broken. While on that commit
>>> it shows 4 files as changed that have not been changed. If I 'git
>>> reset --hard', there is no effect, the files are still shown as
>>> changed. If I 'git checkout <filename>' one of the files, no effect.
>>> If I clone the repository anew, it shows about 100 files as changed in
>>> the master branch (different branch from above). Most of these are
>>> cloned local repository. Same behavior by reset --hard and checkout as
>>> above: no effect. Here's reset:
>>> $ git reset --hard
>>> HEAD is now at 7145157 Neighborhoods list is a one-column list in new
>>> service offering page
>>> $ git st
>>> # On branch master
>>> # Changed but not updated:
>>> # (use "git add <file>..." to update what will be committed)
>>> # (use "git checkout -- <file>..." to discard changes in working
>>> # modified:
>>> ....many more files
>>> 'git fsck' gives no output.
>>> I even did a 'git gc' on my local repository, push it to a new remote
>>> repository and cloned that. The problem is still there!
>>> WTF is going on? I'm losing my mind.
>> 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+...@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
For more options, visit https://groups.google.com/groups/opt_out.