Fix: harden utimes, use single quotes#1109
Merged
spacewander merged 5 commits intotj:mainfrom Nov 23, 2023
Merged
Conversation
hyperupcall
approved these changes
Nov 11, 2023
spacewander
approved these changes
Nov 22, 2023
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
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.
EDIT: I replaced the double quotes with single quotes to stop bash from processing shell meta-characters, such as
$and ` in filenames.EDIT: I also removed passing
--posixto bash, as bash may whine about non-posix code in the user's existing environment. For example, if a user has a function name with a colon in it, bash will complain:bash: line 4: BASH_FUNC_lib:funcname%%': not a valid identifierwhen
--posixis passed.Now works on repos with tricky filenames: