File: OWNERS

package info (click to toggle)
chromium 138.0.7204.183-1
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 6,071,908 kB
  • sloc: cpp: 34,937,088; ansic: 7,176,967; javascript: 4,110,704; python: 1,419,953; asm: 946,768; xml: 739,971; pascal: 187,324; sh: 89,623; perl: 88,663; objc: 79,944; sql: 50,304; cs: 41,786; fortran: 24,137; makefile: 21,806; php: 13,980; tcl: 13,166; yacc: 8,925; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (19 lines) | stat: -rw-r--r-- 657 bytes parent folder | download | duplicates (5) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
 
achuith@chromium.org
hidehiko@chromium.org
jamescook@chromium.org
khorimoto@chromium.org
oshima@chromium.org
xiyuan@chromium.org


# This is for the common case of adding or renaming files. If you're doing
# structural changes, use usual OWNERS rules.
per-file BUILD.gn=*

# We're trying to avoid taking new dependencies on ash. But when they
# happen, we want the chrome-side review to be easy for OWNERS there,
# leaving the ash-side to approve or reject the new dependency.
per-file DEPS=set noparent
per-file DEPS=file://chrome/browser/ash/REFACTORING_OWNERS
per-file .../DEPS=set noparent
per-file .../DEPS=file://chrome/browser/ash/REFACTORING_OWNERS