commit | 62f58991bc4c35ae30a31d17fa5861580b48c09f | [log] [tgz] |
---|---|---|
author | chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> | Fri Mar 29 01:55:21 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Mar 29 01:55:21 2024 |
tree | 8309ef19a8cd643cc5c3c3101cc3883ba036b48b | |
parent | 82990092634df3ef33c519083e9a586701f91d75 [diff] |
Roll optimization-guide from ab04e9f8dc14 to 9e938bc0da51 https://chrome-internal.googlesource.com/chrome/components/optimization_guide.git/+log/ab04e9f8dc14..9e938bc0da51 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/optimization-guide-chromium Please CC chrome-intelligence-core@google.com,sophiechang@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Bug: chromium:331206364 Change-Id: I53d992568569a2bcd37291899e7a4ba0fa73190b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5406594 Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Bot-Commit: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1280036}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.