Update lower-level codereview.settings files.

Update lower-level codereview.settings files.

Every now and then we get CLs to codereview.webrtc.org
that are created from a Chromium checkout by editing
the code in third_party/webrtc or third_party/libjingle.

By editing these lower-level codereview.settings files,
we instead cause a crash during 'git cl upload', but the
contents of the file will also be printed, which can work
as an error message. The alternative would be to entirely
remove the files.

BUG=
R=andrew@webrtc.org, tommi@webrtc.org

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

[kjellander_webrtc, 2015-10-06 19:51:13]

kjellander@webrtc.org changed reviewers:
+ andrew@webrtc.org

[kjellander_webrtc, 2015-10-06 19:51:13]

I'm not entirely sure why we've kept these around for so long, do you remember? 
To me, it only seems like they're causing trouble and extra work for people that
upload patches from Chromium checkouts.

[brucedawson, 2015-10-06 19:55:05]

brucedawson@chromium.org changed reviewers:
+ brucedawson@chromium.org

[brucedawson, 2015-10-06 19:55:06]

Thanks. It's good to catch errors as early as possible and this looks like it
does the job.

[Andrew MacDonald, 2015-10-06 20:58:45]

lgtm

The one advantage of this was allowing Chromium devs to upload CLs which a
webrtc dev could easily patch and land. But that could equally well be viewed as
a disadvantage from the webrtc side :)

Henrik, wasn't there an effort to be able to land webrtc CLs uploaded from
Chromium through the CQ?

[kjellander (google.com), 2015-10-06 21:07:23]

On 2015/10/06 20:58:45, Andrew MacDonald wrote:
> lgtm
> 
> The one advantage of this was allowing Chromium devs to upload CLs which a
> webrtc dev could easily patch and land. But that could equally well be viewed
as
> a disadvantage from the webrtc side :)

Yeah, I think it adds more confusion than benefit. Having this as an "error
message" should point them into the direction of making a CL that actually works
to land right away.

> Henrik, wasn't there an effort to be able to land webrtc CLs uploaded from
> Chromium through the CQ?

I don't think this is possible until we've merged the last parts of talk into
webrtc. Then we can change so that src/third_party/webrtc contains a full WebRTC
repo instead, which would also have other benefits (we could easily setup
trybots that build Chromium + our patch etc).

[kjellander (google.com), 2015-10-06 21:08:55]

kjellander@google.com changed reviewers:
+ tommi@webrtc.org

[kjellander (google.com), 2015-10-06 21:09:06]

kjellander@google.com changed reviewers:
+ kjellander@google.com

[kjellander (google.com), 2015-10-06 21:09:07]

+tommi for talk OWNERS

[tommi, 2015-10-06 21:18:51]

lgtm

[kjellander_webrtc, 2015-10-06 21:19:40]

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

[commit-bot: I haz the power, 2015-10-06 21:19:45]

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