third_party/py_vulcanize/README.chromium - Issue 1376953005: Move tracing/third_party/tvcm -> third_party/py_vulcanize.

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: third_party/py_vulcanize/README.chromium

Issue 1376953005: Move tracing/third_party/tvcm -> third_party/py_vulcanize. (Closed) Base URL: git@github.com:catapult-project/catapult.git@master

Patch Set: Created 5 years, 2 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 Name: py_vulcanize

	2 URL: N/A

	3 Version: N/A

	4

	5 Description:

	6 Py-vulcanize, formerly known as TVCM (trace-viewer component model).
	qyearsley 2015/10/06 17:54:15 Could be written as Py-vulcanize, Py Vulcanize, or Could be written as Py-vulcanize, Py Vulcanize, or something else. sullivan 2015/10/06 18:22:00 I'm okay with any of them, Nat, WDTY? Show quoted text On 2015/10/06 17:54:15, qyearsley wrote: > Could be written as Py-vulcanize, Py Vulcanize, or something else. I'm okay with any of them, Nat, WDTY?
	7 This code doesn't actually live anywhere else currently, but it may

	8 be split out into a separate repository in the future.
	qyearsley 2015/10/06 17:54:15 Not really sure if a README.chromium file is neces Not really sure if a README.chromium file is necessary here - my thought when adding this is that if there's not some kind of README here then people might think that it exists elsewhere but we're missing a README.chromium file. sullivan 2015/10/06 18:22:00 tracing/third_party/tvcm did not have a README.chr Show quoted text On 2015/10/06 17:54:15, qyearsley wrote: > Not really sure if a README.chromium file is necessary here - my thought when > adding this is that if there's not some kind of README here then people might > think that it exists elsewhere but we're missing a README.chromium file. tracing/third_party/tvcm did not have a README.chromium. Nat, do you know the history?
OLD	NEW

« no previous file with comments | « perf_insights/perf_insights_project.py ('k') | third_party/py_vulcanize/py_vulcanize/__init__.py » ('j') | no next file with comments »