commit | d7b8f2a0a573cfd1d50cb626bf4e73e0254d74f8 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Mon Mar 17 21:02:49 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Mar 17 21:02:49 2025 |
tree | d240beaee34d97fb3369183c5434d3e2b4fc6266 | |
parent | fcb5eea9fe5e3f20661e52f6580abf8c64be8879 [diff] |
Roll llvm-libc from 14489e08b2c2 to 7b5c0726f691 (1 revision) https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libc.git/+log/14489e08b2c2..7b5c0726f691 2025-03-17 TheStarOne01@proton.me [libc][docs] Add glob implementation status doc and include in CMakeLists (#126923) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/llvm-libc-chromium Please CC aeubanks@google.com,lexan@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry 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: aeubanks@google.com Change-Id: I3ed8b138903e67a39db17d3fe72c6c85dcdfa6f6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6362917 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@{#1433763}
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.