Auto-Submit | +1 |
@cblume, can you PTAL as one of `//third_party/libpng/OWNERS`?
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Auto-Submit | +1 |
@dcheng, I wonder if you could PTAL (as one of `third_party/blink/renderer/OWNERS` + as a member of Chrome Security team)?
I wonder if using your Owners-Override powers on this CL would be reasonable. This CL is quite mechanical - if the changes pass `gn gen`, `gn check`, and build fine, then restricted dependencies and restricted visibility are surely desirable.
In theory, I could temporarily become an owner of `//third_party/libpng` during its removal (AFAIK @cblume doesn't works on Chrome since 2021, although they usually have been quite responsive and helpful with CLs and bugs). But we just need to land around 4-5 CLs to tighten visibility there, and using Owners-Override or asking //third_party/OWNERS for a review seem like an enticing path of least resistance.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Code-Review | +1 |
Commit-Queue | +2 |
Owners-Override | +1 |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
[rust png] Remove GN-level Blink => libpng dependencies.
Code-level `libpng` dependencies under `third_party/blink` are already
gone at this point (thanks to CLs like https://crrev.com/c/6907475
and/or https://crrev.com/c/6931691). Therefore this CL removes
remaining, obsolete GN-level dependency edges + tightens `visibility`.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |