Don't flag third_party/boringssl as needing README.chromium changes.

Don't flag third_party/boringssl as needing README.chromium changes.

Unlike most things in third_party and like Blink, BoringSSL is unversioned and
maintained by us. It is rolled via DEPS in third_party/boringssl/src, but still
has Chromium-specific build files checked into the third_party/boringssl
directory. Shush presubmit complaining on DEPS rolls when those files change.

The one time we might wish to update README.chromium is if something about the
license changes, but that would be signaled via a DEPS change and not picked up
by this PRESUBMIT rule anyway.

BUG=none

Committed: https://crrev.com/88ace3fa74d1fff50376eb20a3495798758c4eeb
Cr-Commit-Position: refs/heads/master@{#360609}

[davidben, 2015-11-19 00:46:55]

davidben@chromium.org changed reviewers:
+ jochen@chromium.org

[davidben, 2015-11-19 00:46:55]

I'm not sure if this qualifies as an exemption here or not, so I'll defer to
you. It only affects me since I'm the one who rolls BoringSSL, but it means many
BoringSSL rolls I skip presubmits and sometimes miss legitimate ones.

[jochen (gone - plz use gerrit), 2015-11-19 09:22:54]

lgtm

[davidben, 2015-11-19 16:57:23]

The CQ bit was checked by davidben@chromium.org

[commit-bot: I haz the power, 2015-11-19 16:58:04]

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

[commit-bot: I haz the power, 2015-11-19 17:09:57]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-11-19 17:10:56]

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