summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorIttay Stern <ittay.stern@att.com>2019-09-10 13:13:19 +0000
committerGerrit Code Review <gerrit@onap.org>2019-09-10 13:13:19 +0000
commit450eb8f68d26e21f450947fc100ec04380231ddd (patch)
tree7962eb12c183169fe28227903c53727746d55546 /docs
parent895a0097532603726d414395a10e5ad0d99fd7a5 (diff)
Update git submodules
* Update docs/submodules/vid.git from branch 'master' to 3171bdbbf3882ed02d0c4e9807b360035493a197 - Merge changes from topics "VID-14", "VID-13", "VID-12" * changes: Add Semicolon at the end Add Semicolon at the end Add Semicolon ath the end - Add Semicolon at the end In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-607 Change-Id: Ic75affcf10f990fa507eaf738a360df603a700dc Signed-off-by: anushadasari <danush10@in.ibm.com> - Add Semicolon at the end In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-607 Change-Id: I40df40c69bf7de18eeafbf640b4ebe1d0efe6def Signed-off-by: anushadasari <danush10@in.ibm.com> - Add Semicolon ath the end In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line. Issue-ID: VID-607 Change-Id: I9ca9d0f3c935efe83859b4d623939adce0a38465 Signed-off-by: anushadasari <danush10@in.ibm.com>
Diffstat (limited to 'docs')
m---------docs/submodules/vid.git0
1 files changed, 0 insertions, 0 deletions
diff --git a/docs/submodules/vid.git b/docs/submodules/vid.git
-Subproject 1b4336d9c26c4febe86036900bfa7994c0fadca
+Subproject 3171bdbbf3882ed02d0c4e9807b360035493a19