Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upCleanup ports/servo to only rely on libservo #20483
Conversation
highfive
commented
Mar 31, 2018
|
Heads up! This PR modifies the following files:
|
|
Can you remove the commented lines? |
Yep, done. |
|
Arg, tidy was clean locally... what did I miss |
|
@bors-servo r+ |
|
|
Cleanup ports/servo to only rely on libservo <!-- Please describe your changes on the following line: --> When using `ports/servo` as a starting point for an embedding, it's easier if it only relies on the `libservo` crate and not directly on `components` ones. Since `libservo` reexports all the modules we need, it's a straightforward fix. --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: --> - [X] `./mach build -d` does not report any errors - [X] `./mach test-tidy` does not report any errors - [ ] These changes fix #__ (github issue number if applicable). <!-- Either: --> - [ ] There are tests for these changes OR - [X] These changes do not require tests because There are no relevant tests, and no real code change. <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. --> <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/20483) <!-- Reviewable:end -->
|
|
|
|
@bors-servo r+ |
|
|
Cleanup ports/servo to only rely on libservo <!-- Please describe your changes on the following line: --> When using `ports/servo` as a starting point for an embedding, it's easier if it only relies on the `libservo` crate and not directly on `components` ones. Since `libservo` reexports all the modules we need, it's a straightforward fix. --- <!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `__` with appropriate data: --> - [X] `./mach build -d` does not report any errors - [X] `./mach test-tidy` does not report any errors - [ ] These changes fix #__ (github issue number if applicable). <!-- Either: --> - [ ] There are tests for these changes OR - [X] These changes do not require tests because There are no relevant tests, and no real code change. <!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.--> <!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. --> <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/20483) <!-- Reviewable:end -->
|
|
|
|
@bors-servo retry |
|
|
|
|
fabricedesre commentedMar 31, 2018
•
edited by SimonSapin
When using
ports/servoas a starting point for an embedding, it's easier if it only relies on thelibservocrate and not directly oncomponentsones. Sincelibservoreexports all the modules we need, it's a straightforward fix../mach build -ddoes not report any errors./mach test-tidydoes not report any errorsThis change is