commit | 078a9c6d92b2b96fa86dd9ff092c8fac17823489 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Tue Dec 17 20:27:22 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Dec 17 20:27:22 2024 |
tree | 84b7047b968885af399b2dc0d8de1121bad52999 | |
parent | cb18f6a32868838208a0a92d98a3fb0158ec539c [diff] |
Roll BoringSSL from 57c6e688fa05 to 4a82464f4a66 (3 revisions) https://boringssl.googlesource.com/boringssl.git/+log/57c6e688fa05..4a82464f4a66 2024-12-17 davidben@google.com Don't check for __has_include 2024-12-17 davidben@google.com Use std::optional in one place in bssl_shim 2024-12-17 davidben@google.com Replace OPENSSL_FALLTHROUGH with [[fallthrough]] 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: I2b8b463f02014f4d40851cd75b820aa3e7a1304b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6102320 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@{#1397513}
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.