Issue 2070693003: Use the new API to set the BoringSSL time callback.

Issue 2070693003: Use the new API to set the BoringSSL time callback. (Closed)

Created:
4 years, 6 months ago by Taylor Brandstetter

Modified:
4 years, 6 months ago

Reviewers:
pthatcher1

CC:
webrtc-reviews_webrtc.org, tterriberry_mozilla.com

Base URL:
https://chromium.googlesource.com/external/webrtc.git@master

Target Ref:
refs/pending/heads/master

Project:
webrtc

Visibility:
Public.

Use the new API to set the BoringSSL time callback. Committed: https://crrev.com/d685fef94c2b4268b205a3bb08b3c4ff4c25fbfc Cr-Commit-Position: refs/heads/master@{#13224}

Created: 4 years, 6 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+1 line, -2 lines)			Patch
	M	webrtc/base/opensslstreamadapter.cc	View		1 chunk	+1 line, -2 lines	0 comments	Download

Total messages: 8 (3 generated)

commit-bot: I haz the power

CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/2070693003/1

4 years, 6 months ago (2016-06-20 17:37:36 UTC) #5

commit-bot: I haz the power

4 years, 6 months ago (2016-06-20 19:00:52 UTC) #8

Message was sent while issue was closed.

Patchset 1 (id:??) landed as
https://crrev.com/d685fef94c2b4268b205a3bb08b3c4ff4c25fbfc
Cr-Commit-Position: refs/heads/master@{#13224}