commit | 930ca8f54d48bb77e506404af3fe4147c40d6368 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Fri Apr 18 20:24:54 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 18 20:24:54 2025 |
tree | 8f04f5fbdebb037ebb825fe44d9cca141262b0a6 | |
parent | c3bf916542a12531140949bf575cab65e33cdcbe [diff] |
Roll BoringSSL from 999dd48f4d6c to 07a1e6236ee8 (1 revision) https://boringssl.googlesource.com/boringssl.git/+log/999dd48f4d6c..07a1e6236ee8 2025-04-18 davidben@google.com Fix v2i_AUTHORITY_INFO_ACCESS 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: I622f42f6fe6137b3d022c7d3b7c1ebf1d641323a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6471767 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@{#1448994}
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.