Issue 4831 - Optlink should reject invalid characters based on the NTFS filesystem. #1
Conversation
This file contains 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
|
I'm closing this down until Pull #2 is merged so I can properly test this (and maybe add test-cases). |
ghost
closed this
|
Ping @AndrejMitrovic. #2 was merged over a year ago. http://d.puremagic.com/issues/show_bug.cgi?id=4831 still remains open. Can we get some traction on this? Thanks. |
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
http://d.puremagic.com/issues/show_bug.cgi?id=4831
Hopefully this fixes the issue, however since I still can't build Optlink myself I'll have to kindly ask @WalterBright to test this in his spare time.