-
Notifications
You must be signed in to change notification settings - Fork 398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash when Git's core.excludesFile
points to non-existent file
#131
Comments
martinvonz
added a commit
that referenced
this issue
Mar 13, 2022
…issing I thought that `std::fs::canonicalize()` expanded "~", but it doesn't seem to do that, which caused #131. Git seems to do the expansion itself, so we probably also should. More importantly `std::fs::canonicalize()` crashes when the file doesn't exist. The manual expansion we do now does not. Closes #131.
martinvonz
added a commit
that referenced
this issue
Mar 13, 2022
I thought that `std::fs::canonicalize()` expanded "~", but it doesn't seem to do that, which caused #131. Git seems to do the expansion itself, so we probably also should. More importantly `std::fs::canonicalize()` crashes when the file doesn't exist. The manual expansion we do now does not. Closes #131.
martinvonz
added a commit
that referenced
this issue
Mar 13, 2022
I thought that `std::fs::canonicalize()` expanded "~", but it doesn't seem to do that, which caused #131. Git seems to do the expansion itself, so we probably also should. More importantly `std::fs::canonicalize()` crashes when the file doesn't exist. The manual expansion we do now does not. Closes #131.
martinvonz
added a commit
that referenced
this issue
Mar 13, 2022
I thought that `std::fs::canonicalize()` expanded "~", but it doesn't seem to do that, which caused #131. Git seems to do the expansion itself, so we probably also should. More importantly `std::fs::canonicalize()` crashes when the file doesn't exist. The manual expansion we do now does not. Closes #131.
martinvonz
added a commit
that referenced
this issue
Mar 13, 2022
I thought that `std::fs::canonicalize()` expanded "~", but it doesn't seem to do that, which caused #131. Git seems to do the expansion itself, so we probably also should. More importantly `std::fs::canonicalize()` crashes when the file doesn't exist. The manual expansion we do now does not. Closes #131.
martinvonz
added a commit
that referenced
this issue
Mar 13, 2022
I thought that `std::fs::canonicalize()` expanded "~", but it doesn't seem to do that, which caused #131. Git seems to do the expansion itself, so we probably also should. More importantly `std::fs::canonicalize()` crashes when the file doesn't exist. The manual expansion we do now does not. Closes #131.
martinvonz
added a commit
that referenced
this issue
Mar 14, 2022
This release is just to get #131 out and to see if the automated release builds work now that we use a vendored OpenSSL from libgit2.
martinvonz
added a commit
that referenced
this issue
Mar 14, 2022
This release is just to get #131 out and to see if the automated release builds work now that we use a vendored OpenSSL from libgit2.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I had configured
core.excludesFile
in my~/.gitconfig
to point to~/.gitignore
, but I didn't have such a file. That madejj st
in a Git-backed repo crash.Specifications
The text was updated successfully, but these errors were encountered: