commit | 9734ecf158ca2faaafb8773c07822af6ae466136 | [log] [tgz] |
---|---|---|
author | Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> | Mon Apr 14 20:37:35 2025 |
committer | Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> | Mon Apr 14 20:37:35 2025 |
tree | f5ca93f510cb5957c2713626276c41928df07abe | |
parent | 4d9f85ce2905d2db85ad9e3ba006e0789452f71f [diff] |
Roll commits from side projects in M136 Roll src/third_party/devtools-frontend/src in M136 from 66ad26d4a6c2 to 9d6e5b40b59b Commits rolled: https://chromium.googlesource.com/devtools/devtools-frontend/+log/66ad26d4a6c2..9d6e5b40b59b Roll src/third_party/skia in M136 from 8fe43b5dc644 to a8c3455db034 Commits rolled: https://skia.googlesource.com/skia.git/+log/8fe43b5dc644..a8c3455db034 Roll src/v8 in M136 from 1dbf68079948 to 2bc178b8a3fc Commits rolled: https://chromium.googlesource.com/v8/v8.git/+log/1dbf68079948..2bc178b8a3fc Generated by: http://go/bbid/8717582381912809313 Change-Id: I4942203f8b6d01d586ec9d2b66ed4d2d8e2fcee8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6455444 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/7103@{#881} Cr-Branched-From: e09430c64983fc906f37a9f7e6806275c9b67b86-refs/heads/main@{#1440670}
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.