commit | 2d602b9707b9aab83906ca20756404b51a0b7c22 | [log] [tgz] |
---|---|---|
author | Marco Paniconi <marpan@google.com> | Tue Mar 04 17:59:47 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 04 17:59:47 2025 |
tree | 7bd3762bbaa7d6609592d9a3f2cc236d511954f7 | |
parent | 3bbb70f1162afa6e8f87737b1e9ac865a0d8a302 [diff] |
Roll src/third_party/libvpx/source/libvpx/ 2bfb9f9e0..95afae324 (5 commits) https://chromium.googlesource.com/webm/libvpx.git/+log/2bfb9f9e0a9c..95afae324986 $ git log 2bfb9f9e0..95afae324 --date=short --no-merges --format='%ad %ae %s' 2025-02-27 marpan rtc-vp9: Relax the max_qp setting on scene changes. 2025-02-01 zuxy.meng AVX512 implementation of SAD64 2025-02-21 marpan svc: Fix the force keyframe condition in encoder_set_config 2025-02-21 marpan vp9-svc: Fix to reset in cyclic refresh for svc 2025-02-24 jdorfman rtcd: fix unstable application of --require- Created with: roll-dep src/third_party/libvpx/source/libvpx R=jzern@google.com Bug: b:308446709, b:399575647, b:392441185 Change-Id: I090f9e04afcaf03b340c8629db4ceedc5b8403ac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6321728 Commit-Queue: James Zern <jzern@google.com> Reviewed-by: Eugene Zemtsov <eugene@chromium.org> Reviewed-by: James Zern <jzern@google.com> Cr-Commit-Position: refs/heads/main@{#1427815}
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.