chrome/browser/signin/OWNERS - Issue 2744513003: [DirectoryOwnership] Add TEAM/COMPONENT into OWNERS files.

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: chrome/browser/signin/OWNERS

Issue 2744513003: [DirectoryOwnership] Add TEAM/COMPONENT into OWNERS files. (Closed)

Patch Set: Created 3 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

OLD	NEW
1 mlerman@chromium.org	1 mlerman@chromium.org

2 msarda@chromium.org	2 msarda@chromium.org

3 rogerta@chromium.org	3 rogerta@chromium.org

4	4

5 per-file chrome_proximity_auth_*=tbarzic@chromium.org	5 per-file chrome_proximity_auth_*=tbarzic@chromium.org

6 per-file chrome_proximity_auth_*=tengs@chromium.org	6 per-file chrome_proximity_auth_*=tengs@chromium.org

7 per-file chrome_proximity_auth_*=xiyuan@chromium.org	7 per-file chrome_proximity_auth_*=xiyuan@chromium.org

8	8

9 per-file easy_unlock_*=tbarzic@chromium.org	9 per-file easy_unlock_*=tbarzic@chromium.org

10 per-file easy_unlock_*=tengs@chromium.org	10 per-file easy_unlock_*=tengs@chromium.org

11 per-file easy_unlock_*=xiyuan@chromium.org	11 per-file easy_unlock_*=xiyuan@chromium.org

12	12

13 per-file screenlock_bridge*=tbarzic@chromium.org	13 per-file screenlock_bridge*=tbarzic@chromium.org

14 per-file screenlock_bridge*=tengs@chromium.org	14 per-file screenlock_bridge*=tengs@chromium.org

15 per-file screenlock_bridge*=xiyuan@chromium.org	15 per-file screenlock_bridge*=xiyuan@chromium.org

	16

	17 # COMPONENT: UI>ProximityAuth
	msarda 2017/03/10 14:21:26 # TEAM: chrome-signin@chromium.org (I doubt this g # TEAM: chrome-signin@chromium.org (I doubt this group exists now as we were only using a Google internal group. Should I create this group?) # COMPONENT: Services>SignIn easy_unlock* files have a different component though: #TEAM: #COMPONENT: UI>ProximityAuth I think that tengs@ can advise on this. ymzhang1 2017/03/10 18:06:06 Thanks for the comments! I'll add chrome-signin@ch Show quoted text On 2017/03/10 14:21:26, msarda wrote: > # TEAM: mailto:chrome-signin@chromium.org (I doubt this group exists now as we were > only using a Google internal group. Should I create this group?) > # COMPONENT: Services>SignIn > > > easy_unlock* files have a different component though: > #TEAM: > #COMPONENT: UI>ProximityAuth > I think that tengs@ can advise on this. Thanks for the comments! I'll add chrome-signin@chromium.org for now. I maintain a list of component-team(including internal group) yet only public mailing lists will be added in OWNERS files. We would like to add only one primary component in OWNERS file. Many thanks for information about easy_unlock. I'll save this mapping (easy_unlock: UI>ProximityAuth) separately. Team information is also welcome for component UI>ProximityAuth. Thanks!
OLD	NEW

« no previous file with comments | « no previous file | no next file » | no next file with comments »