-
Notifications
You must be signed in to change notification settings - Fork 35
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
Fix chromium links #209
Fix chromium links #209
Conversation
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.
Images on upstream pages are broken. Maybe we need an alternative.
Otherwise LGTM
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.
Just saw rebase is required due to merge conflicts (probably due to #208)
a6468bc
to
0b1008f
Compare
Should be good now |
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.
Can second ninelore. This has to do with the device property (list of device names) PR is very difficult to review with the change in spacing, since it shows every line has changed. If possible, could we restore 4 spacing or use 2 separate commits |
0b1008f
to
839ae2e
Compare
Fixed it |
We have local image links that are 404. ToDo check where they went |
Which images? |
I don't know where the Chromium images went, not seeing anything about it. |
I will investigate it soon dw |
All Chromium docs links in devices.json give 404, as the upstream links seemed to have changed. These are the proper links.