Skip to content
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.

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

Revert "Add correction message type" #748

Merged
merged 1 commit into from
Feb 2, 2018
Merged

Revert "Add correction message type" #748

merged 1 commit into from
Feb 2, 2018

Conversation

Diadlo
Copy link

@Diadlo Diadlo commented Feb 2, 2018

This reverts commit e16d389 and
commit c5976e3.


This change is Reviewable

This reverts commit e16d389 and
commit c5976e3.
@iphydf
Copy link
Member

iphydf commented Feb 2, 2018

:lgtm_strong:


Review status: 0 of 7 files reviewed at latest revision, all discussions resolved.


Comments from Reviewable

@iphydf
Copy link
Member

iphydf commented Feb 2, 2018

Reviewed 7 of 7 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.


Comments from Reviewable

@iphydf iphydf added this to the v0.2.0 milestone Feb 2, 2018
@iphydf iphydf merged commit 99bfb9a into TokTok:master Feb 2, 2018
@LittleVulpix
Copy link

Out of curiosity, why was this reverted?

@SkyzohKey
Copy link

Same question as @LittleVulpix

@Diadlo
Copy link
Author

Diadlo commented Mar 4, 2018

@LittleVulpix @SkyzohKey Read discussion in #685 from this comment

@LittleVulpix
Copy link

Thanks @Diadlo , yeah I think that's fair - though it would have been better if this was linked in the PR summary (instead of just the fact that it's reverting a commit) so that it would be apparent what the motivation was. Still thanks for the explanation!

@Diadlo
Copy link
Author

Diadlo commented Mar 4, 2018

@LittleVulpix Yes, you are right, I'm sorry

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants