CeDeROM wrote: > >> I am planning to test other stuff and make a release so it can be > >> included into openocd submodule infrastructure, > > > > You wil not rework the code so that it can be applied to OpenOCD proper? > > make a libswd-0.4 release that could be included as stable branch > for use with OpenOCD using git submodule architecture :-) Isn't > that proper? :-)
Not really. The way OpenOCD currently uses a submodule for a library that it depends on (instead of depending on a library it depends on) is really ugly. Another instance of same is nothing to strive for. If you want to use and work on libswd also outside of OpenOCD then yes, make a public API for it that you never break, and make a release of libswd the library. Then work on adding support in OpenOCD for using libswd the library. If you want libswd to be added into OpenOCD then prepare commits which apply on top of openocd.git master, and push them to gerrit. This will not be the full commit history of the libswd development of course, lots of libswd commits should be squashed, while others should perhaps be divided into smaller ones, depending on what the libswd commit log looks like. I haven't looked at it. Which approach seems to align better with your plans? //Peter ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
