Add OWNERS for chrome/android/java/res directory.

Add OWNERS for chrome/android/java/res directory.

Changes to these files are always UI-related and should be reviewed by
someone familiar with Chrome Android UI.

Committed: https://crrev.com/98babcf3410e52f785c8ee210de395accaba7894
Cr-Commit-Position: refs/heads/master@{#300990}

[newt (away), 2014-10-23 19:03:57]

newt@chromium.org changed reviewers:
+ dpranke@chromium.org

[newt (away), 2014-10-23 19:03:58]

dpranke: is this OWNERS file valid? I'm trying to specify OWNERS for the "res"
directory, but that directory can't contain a file named OWNERS for
build-related reasons. Is my workaround legit?

[Dirk Pranke, 2014-10-23 19:33:49]

On 2014/10/23 19:03:58, newt wrote:
> dpranke: is this OWNERS file valid? I'm trying to specify OWNERS for the "res"
> directory, but that directory can't contain a file named OWNERS for
> build-related reasons. Is my workaround legit?

Nope, this doesn't work; per-file doesn't reach into subdirectories. 

Why can't you put an OWNERS file in res/ ?

[newt (away), 2014-10-23 20:18:45]

On 2014/10/23 19:33:49, Dirk Pranke wrote:
> On 2014/10/23 19:03:58, newt wrote:
> > dpranke: is this OWNERS file valid? I'm trying to specify OWNERS for the
"res"
> > directory, but that directory can't contain a file named OWNERS for
> > build-related reasons. Is my workaround legit?
> 
> Nope, this doesn't work; per-file doesn't reach into subdirectories. 

Sad :(

> Why can't you put an OWNERS file in res/ ?

Because of how Android's resource processing tool (aapt) works. It processes
every file in the res directory and complains if any files exist that it can't
process.

But now that I've explained this, I just remembered that there is a way to tell
the tool to ignore certain file patterns... So I think that'll work for my
needs.

[Dirk Pranke, 2014-10-23 20:24:04]

On 2014/10/23 20:18:45, newt wrote:
> On 2014/10/23 19:33:49, Dirk Pranke wrote:
> > On 2014/10/23 19:03:58, newt wrote:
> > > dpranke: is this OWNERS file valid? I'm trying to specify OWNERS for the
> "res"
> > > directory, but that directory can't contain a file named OWNERS for
> > > build-related reasons. Is my workaround legit?
> > 
> > Nope, this doesn't work; per-file doesn't reach into subdirectories. 
> 
> Sad :(
> 
> > Why can't you put an OWNERS file in res/ ?
> 
> Because of how Android's resource processing tool (aapt) works. It processes
> every file in the res directory and complains if any files exist that it can't
> process.
>

Yeah, kinda figured it was something like that, but was also thinking that it
would be hard to believe you couldn't filter out something somehow ..
 
> But now that I've explained this, I just remembered that there is a way to
tell
> the tool to ignore certain file patterns... So I think that'll work for my
> needs.

Right-o :).

[newt (away), 2014-10-23 21:57:35]

newt@chromium.org changed reviewers:
+ cjhopman@chromium.org, dtrainor@chromium.org, tedchoc@chromium.org
- dpranke@chromium.org

[newt (away), 2014-10-23 21:57:36]

cjhopman: build/android/gyp
tedchoc/dtrainor: chrome/android/java/res/OWNERS

[David Trainor- moved to gerrit, 2014-10-23 22:05:22]

lgtm

[Ted C, 2014-10-23 22:06:06]

lgtm

[cjhopman, 2014-10-23 22:07:19]

lgtm

[newt (away), 2014-10-23 22:26:05]

The CQ bit was checked by newt@chromium.org

[commit-bot: I haz the power, 2014-10-23 22:27:04]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/647043007/20001

[commit-bot: I haz the power, 2014-10-23 23:52:45]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2014-10-23 23:52:51]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2014-10-23 23:53:18]

Patchset 2 (id:??) landed as
https://crrev.com/98babcf3410e52f785c8ee210de395accaba7894
Cr-Commit-Position: refs/heads/master@{#300990}