commit | 1534f053849da5d9ae0c9459d5130fd4a7204a79 | [log] [tgz] |
---|---|---|
author | chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> | Fri Feb 02 19:44:59 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 02 19:44:59 2024 |
tree | d2407bbe272f3a3fb9817c365190d9a9b15fd996 | |
parent | 908bf407c9dab8d48c8092aa64d209df2146055a [diff] |
Roll optimization-guide from 890a44919fb0 to 16b501826d12 https://chrome-internal.googlesource.com/chrome/components/optimization_guide.git/+log/890a44919fb0..16b501826d12 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: None Change-Id: I2fa0c92dcd4efcb010e6cbf6a204ee4ff6463bf9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5262542 Bot-Commit: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1255708}
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.