AUTHORS - Issue 138413004: Add AUTHORS file for copyright tracking

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: AUTHORS

Issue 138413004: Add AUTHORS file for copyright tracking (Closed) Base URL: https://skia.googlesource.com/skia.git@master

Patch Set: Created 6 years, 11 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
(Empty)
	1 # This is the official list of Skia authors for copyright purposes.

	2 #

	3 # Names should be added to this file as:

	4 # Name or Organization <email address>

	5 # The email address is not required for organizations.

	6

	7 # Please keep the list sorted.

	8

	9 Google Inc.

	10 Intel
	jcgregorio 2014/01/15 21:34:05 Maybe this should be @intel.com ? Actually if we Maybe this should be @intel.com ? Actually if we want to automate this at a later date it would be helpful if it was machine readable also. How about an email address, or email address-like thing followed by a space and then a free form name? tfarina@chromium.org Thiago Fransosi Farina @intel.com Intel @google.com Google Inc. rmistry 2014/01/15 22:28:53 For being easily automatable by systems like CQ I Show quoted text On 2014/01/15 21:34:05, jcgregorio wrote: > Maybe this should be @intel.com ? > > Actually if we want to automate this at a later date it would be helpful if it > was machine readable also. How about an email address, or email address-like > thing followed by a space and then a free form name? > > mailto:tfarina@chromium.org Thiago Fransosi Farina > @intel.com Intel > @google.com Google Inc. For being easily automatable by systems like CQ I would prefer if this was in JSON. Maybe it should contain email: "intel.com", friendly_string (or a better name): "Intel Inc" email: "tfarina@chromium.org", friendly_string (or a better name): "Thiago ..."
	11 NVIDIA

	12 Thiago Fransosi Farina <thiago.farina@gmail.com>

OLD	NEW

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