| commit | 5fc861443457b5af80f77c1c661f8b2320f36bb2 | [log] [tgz] |
|---|---|---|
| author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Wed Sep 18 22:23:03 2024 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 18 22:23:03 2024 |
| tree | e56d0dcb9e1fd94b1450c4459ba96cb9e7f99f81 | |
| parent | 6e2371ef6e2f6770271ce8df287163cbfbdb96fa [diff] |
Roll BoringSSL from 7750d4f1987a to 59c222fcf123 (3 revisions) https://boringssl.googlesource.com/boringssl.git/+log/7750d4f1987a..59c222fcf123 2024-09-18 davidben@google.com runner: Fix up how hpke and kyber get their test data 2024-09-18 agl@imperialviolet.org hex-search-modify: add tool used in FIPS validations. 2024-09-18 agl@imperialviolet.org break-kat.go should have a copyright header. 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: Ic64187803ffee6fa5d8ab7b9a533f64b1b2f5135 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5874718 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@{#1357350}
ChromiumChromium 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.