content/public/OWNERS - Issue 9695028: Add an OWNERS file for src\content by moving the owners that were there for the top level directori…

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: content/public/OWNERS

Issue 9695028: Add an OWNERS file for src\content by moving the owners that were there for the top level directori… (Closed) Base URL: svn://chrome-svn/chrome/trunk/src/

Patch Set: Created 8 years, 9 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

OLD	NEW
1 set noparent

2 avi@chromium.org

3 jam@chromium.org

4 joi@chromium.org	1 joi@chromium.org

5	2

6 # Please include jam@ on all reviews that are adding new interfaces.	3 # Please include jam@ on all reviews that are adding new interfaces.

7 # For other reviews (modifying existing APIs), prefer avi@ or joi@.	4 # For other reviews (modifying existing APIs), prefer avi@ or joi@.
	joth 2012/10/20 19:07:31 this comment implies all content/public changes st this comment implies all content/public changes still must go through either joi, jam or avi. Any reason not to enforce that by keeping the set noparent?
8	5

9 # While the Content API is being worked on (see	6 # While the Content API is being worked on (see

10 # http://dev.chromium.org/developers/content-module/content-api), we have a very	7 # http://dev.chromium.org/developers/content-module/content-api), we have a very

11 # limited set of owners to ensure that the API is consistent. Once the	8 # limited set of owners to ensure that the API is consistent. Once the

12 # implementation is complete, more owners will be added. If this is holding you	9 # implementation is complete, more owners will be added. If this is holding you

13 # up, IM one of the owners above.	10 # up, IM one of the owners above.
	joth 2012/10/20 19:07:31 this comment is probably obsolete now? this comment is probably obsolete now?
OLD	NEW

« no previous file with comments | « content/ppapi_plugin/OWNERS ('k') | content/renderer/OWNERS » ('j') | no next file with comments »