commit | 3f3e9d90a58229ffc88fbf2ec766d752bec977ab | [log] [tgz] |
---|---|---|
author | chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> | Tue Jul 23 02:51:17 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 23 02:51:17 2024 |
tree | 8f28d1de31af196a2d7034a0d85ba7a9eac74a80 | |
parent | a587e39aaed707f9b486ad94ae5d0ee78974b9b6 [diff] |
Roll optimization-guide from 27c76a4fcf19 to c24116f63221 https://chrome-internal.googlesource.com/chrome/components/optimization_guide.git/+log/27c76a4fcf19..c24116f63221 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: I331adff7aa12d3dc1dd1dce3c6e0de750a71591e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5731728 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@{#1331509}
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.