Roll WebRTC, Libjingle

Roll Libjingle 7718:7721

TBR=kjellander@chromium.org

Committed: https://crrev.com/e6771f981b26c4dae30af55a155ffbf3012c5761
Cr-Commit-Position: refs/heads/master@{#305001}

[tommi (sloooow) - chröme, 2014-11-20 08:37:02]

tommi@chromium.org changed reviewers:
+ kjellander@chromium.org

[tommi (sloooow) - chröme, 2014-11-20 09:24:41]

The CQ bit was checked by tommi@chromium.org

[commit-bot: I haz the power, 2014-11-20 09:25:42]

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

[commit-bot: I haz the power, 2014-11-20 10:59:11]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2014-11-20 10:59:56]

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

[kjellander_chromium, 2014-11-20 16:41:34]

lgtm, but since there are WebRTC changes in that range as well, shouldn't we try
to roll both in the same CL for such cases?

[tommi (sloooow) - chröme, 2014-11-21 15:29:40]

On 2014/11/20 16:41:34, kjellander wrote:
> lgtm, but since there are WebRTC changes in that range as well, shouldn't we
try
> to roll both in the same CL for such cases?

Hm... strange. This was generated by the roll script, so I wonder why it didn't
pick up the webrtc changes?