Add agrieve as OWNER for base/android

base/OWNERS

 # About src/base:
 #
 # Chromium is a very mature project, most things that are generally useful are
 # already here, and that things not here aren't generally useful.
 #
 # Base is pulled into many projects. For example, various ChromeOS daemons. So
 # the bar for adding stuff is that it must have demonstrated wide
 # applicability. Prefer to add things closer to where they're used (i.e. "not
 # base"), and pull into base only when needed.  In a project our size,
 # sometimes even duplication is OK and inevitable.
@@ skipping 12 matching lines @@
 thestig@chromium.org
 dcheng@chromium.org
 
 # For Bind/Callback:
 per-file bind*=tzik@chromium.org
 per-file callback*=tzik@chromium.org
 
 # For Android-specific changes:
 per-file *android*=file://base/android/OWNERS
 per-file BUILD.gn=file://base/android/OWNERS
+per-file BUILD.gn=file://build/OWNERS

[Nico, 2016/08/24 18:35:19]

Why should build/OWNERS be owners of base/OWNERS, especially for
Android-specific changes? If you think you should be here, either add ldap, or,
probably better, become a base/android/OWNER?

[agrieve, 2016/08/24 18:42:38]

This is just owners of base/BUILD.gn (not OWNERS). I'll see about just becoming
an android owner though.

 
 # For FeatureList API:
 per-file feature_list*=asvitkine@chromium.org
 per-file feature_list*=isherman@chromium.org
 
 # For bot infrastructure:
 per-file *.isolate=maruel@chromium.org
 per-file *.isolate=tandrii@chromium.org
 per-file *.isolate=vadimsh@chromium.org
 
 # For TCMalloc tests:
 per-file security_unittest.cc=jln@chromium.org