CHANGELOG: update for #12165 , #12264 .#12355
Merged
spzala merged 1 commit intoetcd-io:masterfrom Oct 5, 2020
cfc4n:changelog_gettoken
Merged
CHANGELOG: update for #12165 , #12264 .#12355spzala merged 1 commit intoetcd-io:masterfrom cfc4n:changelog_gettoken
spzala merged 1 commit intoetcd-io:masterfrom
cfc4n:changelog_gettoken
Conversation
Contributor
Contributor
Author
Thanks for reivew. I send two cherry-pick PRs to backport to branch 3.4/3.3 about #12264 , but #12165 can't be auto merged, there is a lot of conflict codes in diff list. I think that I need to send a normal pr for #12165 , And I'll finished it tomorrow. |
Contributor
Member
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
3 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.
CHANGELOG: update for #12165 , #12264 .
Do I need to backport #12165 , #12264 to branch 3.4\3.3 ?
@mitake @spzala @jingyih