| commit | 57707eaff1b9910602888eb12d22ef05600f4928 | [log] [tgz] |
|---|---|---|
| author | chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> | Tue Aug 05 17:17:05 2025 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 05 17:17:05 2025 |
| tree | c24e2734f0993836aa021178ace3e66535c68afc | |
| parent | c696399cf7fba794be50d07ad09c45ec600bcf02 [diff] |
Roll ios_internal from de174e628e48 to 17f72536aae7 https://chrome-internal.googlesource.com/chrome/ios_internal.git/+log/de174e628e48..17f72536aae7 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/ios-internal-chromium-autoroll Please CC chrome-brapp-engprod@google.com,rkgibson@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 Bug: None Change-Id: I5a8d76fb597d0171b4912302c46f69d0bd9d10dd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6821631 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@{#1497008}
ChromiumChromium 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.