The ipc/chromium tree, with the exception of ipc/chromium/src/third_party, was originally a third-party import, but since 2014 or so we've given up on the idea of ever tracking upstream and have heavily modified it, with the general idea of evolving it into first-class Mozilla code. So it makes sense to include it in formatting and linting checks. (It does use Google-style naming conventions, but I don't believe we're linting for that at present.)

The ipc/chromium tree has been forked from its former upstream and heavily modified, so it's safe to reformat and lint. However, ipc/chromium/src/third_party (a copy of libevent) is following its upstream, so that should remain exempt.

Pushed by jedavis@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a615ca514a06 Remove ipc/chromium from the lists of third-party code. r=Ehsan

[ESR Uplift Approval Request] If this is not a sec:{high,crit} bug, please state case for ESR consideration: This is required for easier backporting of patches after the reformatting of ESR using clang-format. User impact if declined: Declining this will negatively impact our developers' ability to easily backport their patches to ESR in the future. Fix Landed on Version: 65 Risk to taking this patch: Low Why is the change risky/not risky? (and alternatives if risky): This is NPOTB. String or UUID changes made by this patch: None

Comment on attachment 9031012 [details] [diff] [review] ESR patch OK for uplift to ESR60 as part of the clang-format project.