commit | c8e2bcaccc0a2c369d94816c035dd9ce63e3fd6f | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Jun 27 00:59:17 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jun 27 00:59:17 2024 |
tree | e17b81e53eaa581f74d2d6b78c67ec8ebcb5fe30 | |
parent | f9951c82a7799fabee430b2e1704caa6283f2ca9 [diff] |
Roll Depot Tools from 459e1a54a563 to f4e8e13e8bc5 (2 revisions) https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/459e1a54a563..f4e8e13e8bc5 2024-06-26 ayatane@google.com [gerrit_util] Add linked account detection for SSO 2024-06-26 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC chops-source-team@google.com,ddoman@google.com,sokcevic@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry 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: ddoman@google.com,sokcevic@google.com Change-Id: Ied092dc07700bef26c5e06cb41c5cf98d280932e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5662036 Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1320120}
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.