Age | Commit message (Collapse) | Author | Files | Lines |
|
Project: vnfrqts/requirements master 247c5c0aa643c6460c260227c3cc33c5720439c1
Merge "VNFRQTS -Requirements Ch4 Std Reqs"
VNFRQTS -Requirements Ch4 Std Reqs
VNFRQTS -Requirements Update chanpter 4b and 4c requirements to std
format
Change-Id: Ia9b5a4eaa9e3cecd80cd5ef7e43d61efb3645b5d
Issue-ID:VNFRQTS-82
Signed-off-by: PATTEN <hp1256@att.com>
|
|
Project: vnfrqts/requirements master 984cafbbd0a68a99e6fc6a4759dc54cdc0a3fda2
VNFRQTS -Requirements Ch7b Std Req
VNFRQTS -Requirements Updated Chapter 7b reqs to std format
Change-Id: I476182bd140f836298528928e89791991bef090f
Issue-ID:VNFRQTS-85
Signed-off-by: PATTEN <hp1256@att.com>
|
|
The submodule path hierarchy needs to support a name used as
hierarchy for lower level repositories or groupIDs AND allow
for a repository at each level eg submodules/appc and
submodules/appc/deployment are both repos. When viewed
in the submodule directory structure in the doc project, a
repository will have .git appended. The above example would
be submodules/appc.git submodules/appc/deployment.git
Change how to guide and convert existing submodule names
Rebased prior change
Change-Id: Ie16b8bbda7562aaaee3c21eb504dc6e293c98cbd
Issue-ID: DOC-33
Signed-off-by: Rich Bennett <rb2745@att.com>
|