no colons in filenames: issues with Git, especially on Windows #104
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Since Git uses colons to separate pathnames from tree ids in several commands, a filename with a colon in it can create additional confusion when scripting Git. Additionally, NTFS filename protection rules on Git on Windows are overly strict, and prevent checkouts when there are any colons in filenames. (Two consequtive colons is what would create an issue.)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since Git uses colons to separate pathnames from tree ids in several commands,
a filename with a colon in it can create additional confusion when scripting Git.
Additionally, NTFS filename protection rules on Git on Windows are overly
strict, and prevent checkouts when there are any colons in filenames. (Two
consequtive colons is what would create an issue.)