Remember: GNU/Linux and other UNIX systems can make files that are case-sensitive, Windows can't make files that are case-sensitive - eviltoast
  • DefederateLemmyMl@feddit.nl
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    4 months ago

    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.

    • lseif@sopuli.xyz
      link
      fedilink
      arrow-up
      2
      ·
      4 months ago

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

      • DefederateLemmyMl@feddit.nl
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        4 months ago

        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:

        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.