Reland Issue 2061423003: Refactor NACK bitrate allocation

Reland Issue 2061423003: Refactor NACK bitrate allocation

This is a reland of https://codereview.webrtc.org/2061423003/
Which was reverted in https://codereview.webrtc.org/2131913003/

The reason for the revert was that some upstream code used
RtpSender::SetTargetBitrate(). I've added that back as a no-op until we
it's been brought up to date.

TBR=tommi@webrtc.org

Committed: https://chromium.googlesource.com/external/webrtc/+/05ce4ae31f635c16e10b68601e7e07fdf7bbb29b

[sprang_webrtc, 2016-07-08 16:53:18]

The CQ bit was checked by sprang@webrtc.org

[commit-bot: I haz the power, 2016-07-08 16:53:23]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[sprang_webrtc, 2016-07-08 17:11:31]

Description was changed from

==========
Reland Issue 2061423003: Refactor NACK bitrate allocation

This is a reland of https://codereview.webrtc.org/2061423003/
Which was reverted in https://codereview.webrtc.org/2131913003/

The reason for the revert was that some upstream code used
RtpSender::SetTargetBitrate(). I've added that back as a no-op until we
it's been brought up to date.

TBR=tommi@webrtc.org
==========

to

==========
Reland Issue 2061423003: Refactor NACK bitrate allocation

This is a reland of https://codereview.webrtc.org/2061423003/
Which was reverted in https://codereview.webrtc.org/2131913003/

The reason for the revert was that some upstream code used
RtpSender::SetTargetBitrate(). I've added that back as a no-op until we
it's been brought up to date.

TBR=tommi@webrtc.org

Committed:
https://chromium.googlesource.com/external/webrtc/+/05ce4ae31f635c16e10b68601...
==========

[commit-bot: I haz the power, 2016-07-08 17:11:32]

Description was changed from

==========
Reland Issue 2061423003: Refactor NACK bitrate allocation

This is a reland of https://codereview.webrtc.org/2061423003/
Which was reverted in https://codereview.webrtc.org/2131913003/

The reason for the revert was that some upstream code used
RtpSender::SetTargetBitrate(). I've added that back as a no-op until we
it's been brought up to date.

TBR=tommi@webrtc.org

Committed:
https://chromium.googlesource.com/external/webrtc/+/05ce4ae31f635c16e10b68601...
==========

to

==========
Reland Issue 2061423003: Refactor NACK bitrate allocation

This is a reland of https://codereview.webrtc.org/2061423003/
Which was reverted in https://codereview.webrtc.org/2131913003/

The reason for the revert was that some upstream code used
RtpSender::SetTargetBitrate(). I've added that back as a no-op until we
it's been brought up to date.

TBR=tommi@webrtc.org

Committed: https://crrev.com/05ce4ae31f635c16e10b68601e7e07fdf7bbb29b
Cr-Commit-Position: refs/heads/master@{#13418}
==========

[commit-bot: I haz the power, 2016-07-08 17:11:33]

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

[sprang_webrtc, 2016-07-08 17:11:33]

Committed patchset #1 (id:1) manually as
05ce4ae31f635c16e10b68601e7e07fdf7bbb29b (presubmit successful).

[aluebs-webrtc, 2016-07-08 18:01:25]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.webrtc.org/2130423002/ by aluebs@webrtc.org.

The reason for reverting is: It keeps breaking upstream..