this post was submitted on 06 Sep 2024
614 points (90.4% liked)

linuxmemes

21198 readers
232 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    [email protected]
    [email protected]
    [email protected]
    614
    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]
    242 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 38 points 2 months ago (1 children)

    To screw with Windows users, you should sometimes put a README.md as well as a README.MD in your git repos. It leads to interesting results.

    [–] [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.