-
Notifications
You must be signed in to change notification settings - Fork 214
Use OP_NAME constant instead of hard coding #328
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
Use OP_NAME constant instead of hard coding #328
Conversation
Ok @rnett , I would really like to simplify the review process to speed up PR merging. In this PR, it looks like 99% of the changes are reformatting again. So here's what I propose:
Let's experiment this out, wdyt? |
772aa17
to
57a3d8e
Compare
Ok, I pushed format-less changes. I'll do the formatting and op generation once you approve it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, I love the size of it now, so simple! :D
Ok to push now new changes that only includes reformatting and regenerated ops, thanks! 👍
Op generation is done. |
@rnett sorry but I think you'll need to rebase again, since we've merged TF2.5 not long ago |
Signed-off-by: Ryan Nett <[email protected]>
Signed-off-by: Ryan Nett <[email protected]>
Signed-off-by: Ryan Nett <[email protected]>
Signed-off-by: Ryan Nett <[email protected]>
98a5052
to
f3bd66a
Compare
@karllessard it's rebased. |
Signed-off-by: Ryan Nett <[email protected]>
Simple fix for op generation, results in lots of changed files.