Fixed shebang and file naming#8
Merged
onespaceman merged 1 commit intoonespaceman:masterfrom Oct 24, 2015
Merged
Conversation
onespaceman
added a commit
that referenced
this pull request
Oct 24, 2015
Fixed shebang and file naming
Owner
|
Thanks. off to bed now. |
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
2 participants
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.
Changed shebang from sh to bash (because we're using double brackets, which aren't supported by sh, and you're really not gonna find a real copy of Bourne Shell outside actual Unix anyways...)
And naming works correctly now (first is -polyfy, second is -polyfy2, third is -polyfy3, etc). Luckily that was only two lines of code.