Recently, we started seeing duplicated "per-file" rules sprinkled in the OWNERS files in child directories. Mainly, these have been getting added out of necessity. Example: https://chromium-review.googlesource.com/c/chromium/src/+/1150815

Strangely, crbug 643390 seems to indicate that it may actually behave this way in some situations. It's not clear why that is.

So, after an offline discussion with several owners and the build infra folks, there was a question as to whether "per-file" rules *should* be recursive. It turns out that, yes, we do want this behavior.

Comment from dpranke:

"It shouldn't be too hard to do so, but it's not trivial, it requires restructuring the existing implementation to look at the tree as a whole rather than just the files in the directory. It's all just changes in a couple of methods in one python class, though."