Community
Participate
Working Groups
This has caused me a bit of hair pulling, it appears that EGit is always case sensitive, that is it wants to track `Readme.txt` and `readme.txt` as separate entities. On a windows machine when you do a pull it errors out when trying to merge in the changes or do a git reset. Also if the repository references `Readme.txt` and you locally you have `readme.txt` and you try to commit it will commit a deletion of `Readme.txt` but NO addition of `readme.txt` A work around for me was in GIT command line set `git config core.ignorecase true`, do a pull then do `git mv Readme.txt readme.txt2; git mv readme.txt2 readme.txt` to ensure the case of my file was matching what was in the repository. This is on: Eclipse Git Team Provider 3.7.1.201504261725-r org.eclipse.egit.feature.group Eclipse EGit I don't quiet fully understand the nuances, I think it has to do with `ignorecase = true` being set by default in SourceTree / Git command line on my co-worker machines - please reach out and I can gather more information. Also see: http://stackoverflow.com/a/23960663/913223
To clarify, I think the solution should ensure the JGIT honors the `ignorecase = true` setting in `.git/config` and that there is a way to set it through the EGit preferences.
On that note the UI is a confusing. I've been using EGit for a year now and just now learned that to get to the Repository Settings for EGit you click 'Window > Preferences > Team > Git > Configuration > Tab: Repository Settings' instead of the convention to simply right click the project root node choosing EGit preferences. I have filled this as bug #474234: https://bugs.eclipse.org/bugs/show_bug.cgi?id=474234
Created attachment 255655 [details] egit-sensitivity-nightmare
On current project this is issue make EGit unusable and our team must result to SourceTree - can you please have somebody look into it.
I agree. On a windows system I'm forced to use another git client, or use the command line. I like to use giteye, but this bug is a deal breaker for our group. If this can't be fixed, then at least make git mv an option over the UI (somehow). Almost all the development work at my company is on Windows machines, and I wont be able to sway anyone without this feature.
