Remove assertion over fetch refspec when explicitly specified#402
Merged
Byron merged 1 commit intogitpython-developers:masterfrom Apr 14, 2016
rrei:master
Merged
Remove assertion over fetch refspec when explicitly specified#402Byron merged 1 commit intogitpython-developers:masterfrom rrei:master
Byron merged 1 commit intogitpython-developers:masterfrom
rrei:master
Conversation
Member
|
Thanks a lot for your contribution ! It's much appreciated, and if you need a release with it please let me know. |
Contributor
Author
|
Glad I could help out, even if only a tiny bit :) |
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.
As we discussed in issue #396, the repo's fetch refspec is now only required if no explicit refspec was given as argument to
Remote.fetch()orRemote.pull().