-
Notifications
You must be signed in to change notification settings - Fork 709
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
Remove -upstream
component of SDK names
#1166
Conversation
dc82f07
to
fa3aa8f
Compare
Is this a breaking change? If so, can we strip |
Yes, the |
Because the old names are still supported I think this is a backwards compatible change. |
Sounds good. Not sure why the tests fail then, you are right that that line should be stripping the suffix. |
fa3aa8f
to
277a695
Compare
ping.. ok to land once tests pass? |
277a695
to
30a8ca5
Compare
Lgtm, but please add a test (or keep one) that checks we strip |
This name existed to distinguish the SDK from fastcomp, but as of #1165, we no longer support fastcomp.
30a8ca5
to
0288a20
Compare
The name `upstream` doesn't have any meaning anymore now that there is no more fastcomp. It was removed from the SDK names in #1166 and this is the last usage of that name/term.
The name `upstream` doesn't have any meaning anymore now that there is no more fastcomp. It was removed from the SDK names in #1166 and this is the last usage of that name/term.
The name `upstream` doesn't have any meaning anymore now that there is no more fastcomp. It was removed from the SDK names in #1166 and this is the last usage of that name/term.
The name `upstream` doesn't have any meaning anymore now that there is no more fastcomp. It was removed from the SDK names in #1166 and this is the last usage of that name/term.
This name existed to distinguish the SDK from fastcomp, but as of emscripten-core#1165, we no longer support fastcomp.
This name existed to distinguish the SDK from fastcomp, but as of #1165, we no longer support fastcomp.