Fix a regression in the cooperation between FSCache and long paths #2514
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
In 4d3d891 (squash! Win32: add a cache below mingw's lstat and dirent implementations, 2013-10-01), we adjusted the FSCache feature to accommodate for the `en/fill-directory-fixes` patches, which insist on POSIX-like semantics where `struct dirent`'s `name` entry must be a `char` array and cannot be a `char` pointer. However, when squashing this adjustment into the appropriate patch during the nex rebase (which resulted in 1fcade1 (mingw: add a cache below mingw's lstat and dirent implementations, 2013-10-01)), this developer failed to split out the `MAX_LONG_PATH` part into the appropriate patch but by mistake dropped it instead. This patch fixes that, addressing git-for-windows#2494. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
1 task
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.
This fixes the bug reported at #2494.