duplicate filename in case insensitive filesystem (Windows)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.2k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Hi.
I've just cloned the repository on a Windows machine and noticed that Commit: 920eed79b3fdf1a638ab4a9dbe264bbde5f0c6bd introduced an issue.
File named lib/sw_services/xilpm/doc/XilPM.pdf was originally present, and the commit introduced (probably by mistake) file lib/sw_services/xilpm/doc/xilpm.pdf (all lowercase), which Windows merges with the previous file. Thus, just after the clone operation, I see this as an uncommitted change.
This issue is similar to what is described in https://www.hanselman.com/blog/GitIsCasesensitiveAndYourFilesystemMayNotBeWeirdFolderMergingOnWindows.aspx
Thanks.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect commit 920eed79b3fdf1a638ab4a9dbe264bbde5f0c6bd and compare lib/sw_services/xilpm/doc/XilPM.pdf with lib/sw_services/xilpm/doc/xilpm.pdf. Remove or correct the duplicate filename, then verify that a fresh clone on Windows does not produce an uncommitted change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100