this post was submitted on 06 Sep 2024
615 points (90.6% liked)

linuxmemes

20880 readers
9 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
615
Remember: GNU/Linux and other UNIX systems can make files that are case-sensitive, Windows can't make files that are case-sensitive (lemmy.world)
submitted 2 months ago by [email protected] to c/[email protected]
237 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 2 months ago (1 children)

surely Git warns about stuff like this when you clone it, right ?

[–] [email protected] 4 points 2 months ago (1 children)

It tells you there's a name clash, and then it clones it anyway and you end up with the contents of README.MD in README.md as an unstaged change.

[–] [email protected] 2 points 2 months ago (1 children)

sounds like actually a good solution ... tho doesnt sound like it would work for more than 2 similarly-named files

[–] [email protected] 3 points 2 months ago (1 children)

I 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.

[–] [email protected] 1 points 2 months ago

thats better than Git just choosing a file to keep.