| OLD | NEW |
|---|
| (Empty) |
| 1 mark@chromium.org | |
| 2 thakis@chromium.org | |
| 3 danakj@chromium.org | |
| 4 rvargas@chromium.org | |
| 5 thestig@chromium.org | |
| 6 | |
| 7 # Chromium is a very mature project, most things that are generally useful are | |
| 8 # already here, and that things not here aren't generally useful. | |
| 9 # | |
| 10 # Base is pulled into many projects. For example, various ChromeOS daemons. So | |
| 11 # the bar for adding stuff is that it must have demonstrated wide | |
| 12 # applicability. Prefer to add things closer to where they're used (i.e. "not | |
| 13 # base"), and pull into base only when needed. In a project our size, | |
| 14 # sometimes even duplication is OK and inevitable. | |
| 15 # | |
| 16 # Adding a new logging macro DPVELOG_NE is not more clear than just | |
| 17 # writing the stuff you want to log in a regular logging statement, even | |
| 18 # if it makes your calling code longer. Just add it to your own code. | |
| 19 | |
| 20 per-file *.isolate=maruel@chromium.org | |
| 21 per-file *.isolate=tandrii@chromium.org | |
| 22 per-file *.isolate=vadimsh@chromium.org | |
| 23 per-file security_unittest.cc=jln@chromium.org | |
| 24 | |
| 25 # For Android-specific changes: | |
| 26 per-file *android*=nyquist@chromium.org | |
| 27 per-file *android*=rmcilroy@chromium.org | |
| 28 per-file *android*=yfriedman@chromium.org | |
| OLD | NEW |
|---|
Chromium Code Reviews
