<snip> > > On Wed, Apr 6, 2022 at 8:26 PM Juraj Linkeš <juraj.lin...@pantheon.tech> > wrote: > > > > These are the basic libraries that other libraries depend on. There's > > also the basic framework functionality related to test execution. > > > > Juraj Linkeš (15): > > dts: merge DTS dep/tclclient.tgz to DPDK > > dts: merge DTS dep/tgen.tgz to DPDK > > dts: merge DTS dts to DPDK > > dts: merge DTS framework/__init__.py to DPDK > > dts: merge DTS framework/asan_test.py to DPDK > > dts: merge DTS framework/checkCase.py to DPDK > > dts: merge DTS framework/dts.py to DPDK > > dts: merge DTS framework/exception.py to DPDK > > dts: merge DTS framework/logger.py to DPDK > > dts: merge DTS framework/packet.py to DPDK > > dts: merge DTS framework/project_dpdk.py to DPDK > > dts: merge DTS framework/serializer.py to DPDK > > dts: merge DTS framework/utils.py to DPDK > > dts: merge DTS main.py to DPDK > > dts: merge DTS version.py to DPDK > > merge->import > > > > > dts/dep/tclclient.tgz | Bin 0 -> 199327 bytes > > dts/dep/tgen.tgz | Bin 0 -> 134392 bytes > > Some top level comments: > - I think, we should not check in binary files. > - git commit comment should much more than "dts: merge DTS xxxx to DPDK" > where the commit log should have details on check in. > -Add the documentation from the first patch and update the documentation > per patch based on the content. The documentation is existing documentation. It has evolved based on how the code has evolved. I do not think it is possible to split that documentation now and bring it in on a per patch basis. The best way would be to maintain the history from git.
Some documentation is also getting updated, but this is one time overall update.
