Remember: GNU/Linux and other UNIX systems can make files that are case-sensitive, Windows can't make files that are case-sensitive
Remember: GNU/Linux and other UNIX systems can make files that are case-sensitive, Windows can't make files that are case-sensitive
![](https://lemmy.world/pictrs/image/e5cb8b7b-dc6a-4911-bcb9-6722ac787144.png?thumbnail=1024&format=webp)
You're viewing a single thread.
38 1 Replysurely Git warns about stuff like this when you clone it, right ?
2 0 ReplyIt tells you there's a name clash, and then it clones it anyway and you end up with the contents of
README.MD
inREADME.md
as an unstaged change.2 0 Replysounds like actually a good solution ... tho doesnt sound like it would work for more than 2 similarly-named files
1 0 ReplyI don't think it's intended as a "solution", it just lets the clobbering that is caused by the case insensitiveness happen.
So git just goes:
- checkout content of README.md to README.md (OS creates README.md)
- checkout content of README.MD to README.MD (OS overwrites README.md)
If you add a third or fourth file ... it would just continue, and file gets checked out first gets the filename and whichever file gets checked out last, gets the content.
1 0 Reply