commit | 10cf7adfe5ef348ecf68ecafe7083595d000632a | [log] [tgz] |
---|---|---|
author | chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> | Wed Mar 26 05:28:03 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 26 05:28:03 2025 |
tree | ec7ad8548a8bd69b40af951f6862fb9a54fbaf85 | |
parent | 27a29227eb3d39acb3c06a3c7be49fcb1904592c [diff] |
Roll src-internal from f6341d1ed688 to e64fd5f60a57 (1 revision) https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/f6341d1ed688..e64fd5f60a57 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC chrome-browser-infra-team,hayato@google.com 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 Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: hayato@google.com Change-Id: I005308d54f6ceafdcb2fa27d722dd3f5d4f59ec5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6396159 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@{#1437942}
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.