Remove nick@chromium.org from OWNERS

https://memegen.googleplex.com/5329863038205952

Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: I040c5f5986884cad2ca2b194a06366e8fd12255f
Reviewed-on: https://chromium-review.googlesource.com/1246420Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Nick Carter <nick@chromium.org>
Commit-Queue: Nick Carter <nick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#594784}

chrome/browser/OWNERS

@@ -92,7 +92,6 @@ per-file shell_integration_linux*=thomasanderson@chromium.org
 
 per-file site_details*=creis@chromium.org
 per-file site_details*=nasko@chromium.org
-per-file site_details*=nick@chromium.org
 
 per-file site_per_process_interactive_browsertest.cc=file://content/OWNERS
 per-file site_per_process_interactive_browsertest.cc=kenrb@chromium.org

chrome/browser/task_manager/OWNERS

 afakhry@chromium.org
-nick@chromium.org
 
 # COMPONENT: UI>TaskManager

chrome/browser/ui/task_manager/OWNERS

 afakhry@chromium.org
-nick@chromium.org
 
 # COMPONENT: UI>TaskManager

content/OWNERS

@@ -8,7 +8,6 @@ jam@chromium.org
 jochen@chromium.org
 kinuko@chromium.org
 nasko@chromium.org
-nick@chromium.org
 pfeldman@chromium.org
 piman@chromium.org
 

docs/clang_format.md

@@ -58,8 +58,7 @@ standards apply, it will be enforced by a PRESUBMIT.py check.
 ## Reporting problems
 
 If clang-format is broken, or produces badly formatted code, please file a
-[bug]. Assign it to thakis@chromium.org or nick@chromium.org who will route it
-upstream.
+[bug]. Assign it to thakis@chromium.org who will route it upstream.
 
 [bug]:
-https://code.google.com/p/chromium/issues/entry?comment=clang-format%20produced%20code%20that%20(choose%20all%20that%20apply):%20%0A-%20Doesn%27t%20match%20Chromium%20style%0A-%20Doesn%27t%20match%20blink%20style%0A-%20Riles%20my%20finely%20honed%20stylistic%20dander%0A-%20No%20sane%20human%20would%20ever%20choose%0A%0AHere%27s%20the%20code%20before%20formatting:%0A%0A%0AHere%27s%20the%20code%20after%20formatting:%0A%0A%0AHere%27s%20how%20it%20ought%20to%20look:%0A%0A%0ACode%20review%20link%20for%20full%20files/context:&summary=clang-format%20quality%20problem&cc=thakis@chromium.org,%20nick@chromium.org&labels=Type-Bug,Build-Tools,OS-?
+https://code.google.com/p/chromium/issues/entry?comment=clang-format%20produced%20code%20that%20(choose%20all%20that%20apply):%20%0A-%20Doesn%27t%20match%20Chromium%20style%0A-%20Doesn%27t%20match%20blink%20style%0A-%20Riles%20my%20finely%20honed%20stylistic%20dander%0A-%20No%20sane%20human%20would%20ever%20choose%0A%0AHere%27s%20the%20code%20before%20formatting:%0A%0A%0AHere%27s%20the%20code%20after%20formatting:%0A%0A%0AHere%27s%20how%20it%20ought%20to%20look:%0A%0A%0ACode%20review%20link%20for%20full%20files/context:&summary=clang-format%20quality%20problem&cc=thakis@chromium.org&labels=Type-Bug,Build-Tools,OS-?

services/network/OWNERS

@@ -8,7 +8,6 @@ tsepez@chromium.org
 yhirano@chromium.org
 
 per-file cross_origin_read_blocking*=creis@chromium.org
-per-file cross_origin_read_blocking*=nick@chromium.org
 per-file cross_origin_read_blocking*=lukasza@chromium.org
 
 per-file expect_ct_reporter*=estark@chromium.org

testing/buildbot/OWNERS

@@ -16,7 +16,6 @@ thakis@chromium.org
 
 # For Site Isolation FYI tests:
 per-file chromium.fyi.json=creis@chromium.org
-per-file chromium.fyi.json=nick@chromium.org
 
 per-file chromium.clang.json=hans@chromium.org
 per-file *chromium.perf*.json=dtu@chromium.org

third_party/WebKit/LayoutTests/external/wpt/fetch/corb/OWNERS

@@ -3,4 +3,3 @@
 # WPT-NOTIFY: true
 creis@chromium.org
 lukasza@chromium.org
-nick@chromium.org

third_party/expat/OWNERS

-nick@chromium.org
 dominicc@chromium.org