| commit | 38f28bb43f67127798b7aa319768da0ae5d9aa7e | [log] [tgz] |
|---|---|---|
| author | chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> | Fri Feb 23 06:15:49 2024 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 23 06:15:49 2024 |
| tree | 4c55782f17a29e5874f81faaddd78b04ee805297 | |
| parent | 4442db61b2a29cfa69520d943c427542237d664d [diff] |
Roll clank/internal/apps from e36387909f12 to bbb6e540fb70 (1 revision) https://chrome-internal.googlesource.com/clank/internal/apps.git/+log/e36387909f12..bbb6e540fb70 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/clank-apps-chromium-autoroll Please CC chrome-brapp-engprod@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 Tbr: No-Try: true Change-Id: I886f0c82e4dda89b6baf06a7290d41bcf75d05fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5320208 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@{#1264427}
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.