| commit | 518829b82097e204c092bf8fc6db51da8457f7ab | [log] [tgz] |
|---|---|---|
| author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Jan 23 23:39:06 2025 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 23 23:39:06 2025 |
| tree | 47fba2d12a743947c7ac0231fc320f3791fac688 | |
| parent | 8c7989879959548cebdc170f4eb9f1aca0b67222 [diff] |
Roll BoringSSL from f7febd26f8b6 to 5823b5e1b1e9 (1 revision) https://boringssl.googlesource.com/boringssl.git/+log/f7febd26f8b6..5823b5e1b1e9 2025-01-23 davidben@google.com runner: Make -expect-selected-credential's default more convenient If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/boringssl-chromium Please CC boringssl-cabal@google.com,boringssl@google.com on the revert to ensure that a human is aware of the problem. To file a bug in BoringSSL: https://crbug.com/boringssl/new To file a bug in Chromium: https://crbug.com/new 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 Tbr: boringssl-cabal@google.com Change-Id: I0b81b86842523ab60a13226fcb55137665268d7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6195029 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@{#1410605}
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.