Flag options in git_stash_apply and git_stash_pop as being optional#4117
Merged
ethomson merged 1 commit intolibgit2:masterfrom Feb 10, 2017
Merged
Flag options in git_stash_apply and git_stash_pop as being optional#4117ethomson merged 1 commit intolibgit2:masterfrom
ethomson merged 1 commit intolibgit2:masterfrom
Conversation
The options parameter in both git_stash_apply and git_stash_pop can be NULL. They should be flagged as such in the documentation.
Member
|
👍 Thanks! |
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.
The options parameter in both git_stash_apply and git_stash_pop can be
NULLas can be seen in the linked tests. The documentation in thestash.hheader file should reflect this.