Fix github-merge with git version 2.1.0#4731
Merged
laanwj merged 1 commit intobitcoin:masterfrom Aug 21, 2014
Merged
Conversation
Running git version 2.1.0 on OSX (homebrew), I get fatal: '1q': not a non-negative integer I'm guessing git command-line parsing got more strict recently?
|
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/p4731_c53b1ece1b0644bd9620773eea3757bf939a678f/ for binaries and test log. |
Member
|
Heh, I can't even find a |
Member
|
Looks like for git -q in general means 'quiet mode' mode, but I cannot find it documented for |
laanwj
added a commit
that referenced
this pull request
Aug 21, 2014
c53b1ec Fix github-merge with git version 2.1.0 (Gavin Andresen)
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Running git version 2.1.0 on OSX (homebrew), I get
fatal: '1q': not a non-negative integer
I'm guessing git command-line parsing got more strict recently?