commit | 2a8c13f005937a03e8effd966d76f6b1cd977db9 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Thu Sep 08 16:00:03 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Sep 08 16:00:03 2022 |
tree | 8109d30e05c75b4d604576dbf43ee2927bb2ddff | |
parent | fc0b15acbba542f8d91591bcbe91a98f465aac43 [diff] |
Roll WebRTC from 399a2b5ef6cb to 2fc8c1f7e769 (2 revisions) https://webrtc.googlesource.com/src.git/+log/399a2b5ef6cb..2fc8c1f7e769 2022-09-08 jansson@webrtc.org Update weetbix to its product name 2022-09-08 danilchap@webrtc.org Update android peer connection factory wrapper away from rtc::MessageHandler If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human is aware of the problem. To file a bug in WebRTC: https://bugs.chromium.org/p/webrtc/issues/entry 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: Iad64773cc030e7443988f0275ebf02ada78e7cbf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3881261 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@{#1044577}
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.