| commit | fe5465eb24256dfb11f5f98339d7b4858ffbdb2c | [log] [tgz] |
|---|---|---|
| author | chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> | Tue Dec 24 03:34:36 2024 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 24 03:34:36 2024 |
| tree | 14c420ce0473f6ec6da21cc8b03df502121b1928 | |
| parent | 4aaa26faebb136167ad76893dfa18b1353282f81 [diff] |
Roll eche_app from LmlIDNgYeKOXhaOkr... to M_1CfMKq6XUN4t8wG... Release_Notes: http://go/eche-x20/relnotes/Main/eche_20241223_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/eche_app/app/+/M_1CfMKq6XUN4t8wGbaliKqNzQVXvu1-UM01udITNy0C If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/eche-app-chromium Please CC christyfranks@google.com,dnishi@google.com,eche-app@grotations.appspotmail.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: eche-app@grotations.appspotmail.com Change-Id: I0c1eccc8d14ae8f0c06e82c5802d273e961e683d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6121179 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@{#1399973}
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.