| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Make p_getcwd match the rest of our win32 path handling semantics. (This is currently only used in tests, which is why this disparity went unnoticed.)
When `git_repository_hashfile` is handed an absolute path, it determines whether the path is within the repository's working directory or not. This is necessary when there is no `as_path` specified. If the path is within the working directory, then the given path should be used for attribute lookups (it is the effective `as_path`). If it is not within the working directory, then it is _not_ eligible. Importantly, now we will _never_ pass an absolute path down to attribute lookup functions.
Resolve absolute paths to be working directory relative when looking up attributes. Importantly, now we will _never_ pass an absolute path down to attribute lookup functions.
Always pass a working-directory relative path to attribute lookups during checkout.
Attribute lookups are done on paths relative to the repository. Fail if erroneously presented with an absolute path.
| Back | FazBrowse Home | New Git URL |
We previously (erroneously) passed absolute paths to attribute lookup functions. This sometimes led to ridiculous paths being constructed, like taking an absolute path within a workdir and prefixing the workdir to it. Always provide attribute lookups with a relative path, and enforce in the attribute lookup code that we have done so.