Commit 1ef0493b authored by George Burgess IV's avatar George Burgess IV Committed by Commit Bot

[Docs] Add a note about subdirectories+per-file directives

I tripped over this, causing presubmit breakages:
https://crrev.com/c/884981. In retrospect, this is sort of obvious (and
would be if I looked at the comments in the source), but...

Bug: None
Test: Looked at the new file in gitiles
Change-Id: I5aac9a0da52b34b15d8947062811779bfeeb070f
Reviewed-on: https://chromium-review.googlesource.com/884988Reviewed-by: default avatarLei Zhang <thestig@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
Cr-Commit-Position: refs/heads/master@{#532174}
parent b480abab
...@@ -217,6 +217,13 @@ per-file foo.*=a@chromium.org ...@@ -217,6 +217,13 @@ per-file foo.*=a@chromium.org
per-file readme.txt=* per-file readme.txt=*
``` ```
Note that `per-file` directives cannot directly specify subdirectories, e.g:
```
per-file foo/bar.cc=a@chromium.org
```
is not OK; instead, place a `per-file` directive in `foo/OWNERS`.
Other `OWNERS` files can be included by reference by listing the path to the Other `OWNERS` files can be included by reference by listing the path to the
file with `file://...`. This example indicates that only the people listed in file with `file://...`. This example indicates that only the people listed in
`//ipc/SECURITY_OWNERS` can review the messages files: `//ipc/SECURITY_OWNERS` can review the messages files:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment