commit | 52b6f1ce0943f3d70098116a03919c73c46cb7a2 | [log] [tgz] |
---|---|---|
author | chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> | Tue Oct 29 19:39:02 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 29 19:39:02 2024 |
tree | 1703c7e3209847b15948e6ecdb50dc29b86863ef | |
parent | 6e73241d8af994ac6df334b03b98e9f6752f5157 [diff] |
Roll eche_app from upK9doM1d2odvR-oJ... to 6zcJxY-jmkXFz-hpd... Release_Notes: http://go/eche-x20/relnotes/Main/eche_20241028_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/eche_app/app/+/6zcJxY-jmkXFz-hpdg8vhGfwsEIA1PM1VXlbu-S9bRIC 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: Ic85b696c549d7c29e0640348aa86e6ddec06eefe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5975107 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@{#1375446}
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.