Skip to content

explanation why mutations of tracestate are not required #164

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Aug 24, 2018
Merged

explanation why mutations of tracestate are not required #164

merged 2 commits into from
Aug 24, 2018

Conversation

SergeyKanzhelev
Copy link
Member

Closes #117 and #80 for now.

bogdandrutu
bogdandrutu approved these changes Aug 23, 2018
View reviewed changes
Copy link
Contributor

@bogdandrutu bogdandrutu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is a good idea to not require the tracestate mutation.

@SergeyKanzhelev SergeyKanzhelev changed the title exmaplantion wwhy mutations of tracestate are not required explanation why mutations of tracestate are not required Aug 23, 2018
@SergeyKanzhelev
Copy link
Member Author

I'll wait with the merge to give opportunity for comments

@SergeyKanzhelev SergeyKanzhelev merged commit 061c7c7 into master Aug 24, 2018
@SergeyKanzhelev SergeyKanzhelev mentioned this pull request Aug 24, 2018
Closed
@bogdandrutu bogdandrutu deleted the sergkanz/explanaitionOfNotRequiringMutations branch October 12, 2018 01:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@bogdandrutu bogdandrutu bogdandrutu approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@SergeyKanzhelev @bogdandrutu