commit | 46d65e2c2cc0ab79828627a4024c396fe6b45b32 | [log] [tgz] |
---|---|---|
author | Jonas Olsson <jonasolsson@webrtc.org> | Tue Sep 04 13:42:08 2018 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Tue Sep 04 13:42:20 2018 +0000 |
tree | 5be7849afd885786d8e826692dfa7fc03be92a75 | |
parent | 4c6747c9db5f2deff9b9e670e295b07814834781 [diff] |
Revert "Consolidate loggability checks and replace streams." This reverts commit 4092cd6db459ab8152588143b7b76e0946d2c433. Reason for revert: Some g3 things depend on log macro implementation details. Original change's description: > Consolidate loggability checks and replace streams. > > Currently we check if a message should be printed at the call site using LogMessage::Loggable, in the LogMessage itself using LogMessage::IsNoop and in LogMessage::OutputToDebug using log_to_stderr_. > > This change unifies the first two of these into a early return in Log(). > > Bug: webrtc:8982 > Change-Id: Ia4e3e12b34716d76c05807e44db1ed4a62dffb87 > Reviewed-on: https://webrtc-review.googlesource.com/97440 > Commit-Queue: Jonas Olsson <jonasolsson@webrtc.org> > Reviewed-by: Karl Wiberg <kwiberg@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#24547} TBR=kwiberg@webrtc.org,jonasolsson@webrtc.org Change-Id: I06f0a5b50c96c08a5e7be4d8d2bcb22d50c0179f No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:8982 Reviewed-on: https://webrtc-review.googlesource.com/97720 Reviewed-by: Jonas Olsson <jonasolsson@webrtc.org> Commit-Queue: Jonas Olsson <jonasolsson@webrtc.org> Cr-Commit-Position: refs/heads/master@{#24553}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.