chrome/browser/android/DEPS - Issue 2406203003: Added blimp support strings.

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/android/DEPS

Issue 2406203003: Added blimp support strings. (Closed)

Patch Set: Add entry in translation expectation script. Created 4 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

« blimp/client/support/resources/blimp_strings.grd ('K') | « blimp/client/support/resources/translations/blimp_strings_zh-TW.xtb ('k') | chrome/browser/android/blimp/chrome_blimp_client_context_delegate.cc » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
1 include_rules = [	1 include_rules = [

2 "+blimp/client/public",	2 "+blimp/client/public",

	3 "+blimp/client/support/resources",
	Lei Zhang 2016/10/13 18:09:48 I'm curious, this is for blimp/client/support/reso I'm curious, this is for blimp/client/support/resources/blimp_strings.h right? Why not put the header in b/c/public? xingliu 2016/10/13 21:00:14 Support strings is optional for the embedder. Th Show quoted text On 2016/10/13 18:09:48, Lei Zhang wrote: > I'm curious, this is for blimp/client/support/resources/blimp_strings.h right? > Why not put the header in b/c/public? Support strings is optional for the embedder. There will be another CL setup resources in public.
3 "-components/devtools_bridge",	4 "-components/devtools_bridge",

4 "+cc/layers/layer.h",	5 "+cc/layers/layer.h",

5 "+cc/output/context_provider.h",	6 "+cc/output/context_provider.h",

6 "+components/ntp_snippets",	7 "+components/ntp_snippets",

7 "+components/spellcheck/browser",	8 "+components/spellcheck/browser",

8 "+components/sync/android",	9 "+components/sync/android",

9 "+components/sync/test/fake_server/android",	10 "+components/sync/test/fake_server/android",

10 "+components/toolbar",	11 "+components/toolbar",

11 "+components/web_contents_delegate_android",	12 "+components/web_contents_delegate_android",

12 "+sandbox/linux/seccomp-bpf/sandbox_bpf.h",	13 "+sandbox/linux/seccomp-bpf/sandbox_bpf.h",

13 ]	14 ]

14	15

15 specific_include_rules = {	16 specific_include_rules = {

16 # Special-case where monochrome composes chrome+webview	17 # Special-case where monochrome composes chrome+webview

17 "monochrome_entry_point\.cc": [	18 "monochrome_entry_point\.cc": [

18 "+android_webview",	19 "+android_webview",

19 ]	20 ]

20 }	21 }

OLD	NEW