<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I agree. We have both submodules and the tests in the MPICH repository (for separate things obviously) and I can say that while our use of submodules makes sense (we don’t want to include all of libfabric in the MPICH tree), it’s a pain. Having the tests in the same repo makes sense. I can think of <i class="">other</i> projects that keep the test bucket separate, but I think it’s usually for license reasons rather than cleanliness. <br class=""><div class=""><br class=""></div><div class=""><div class="">Thanks,</div><div class="">Wesley</div></div><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 25, 2018, at 7:28 AM, Jeff Squyres (jsquyres) <<a href="mailto:jsquyres@cisco.com" class="">jsquyres@cisco.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">My $0.02: don't use git submodule. It's more complicated than you think.<br class=""><br class="">Merging the repos would be fine with me.<br class=""><br class=""><br class=""><blockquote type="cite" class="">On Aug 25, 2018, at 1:47 AM, Jeff Hammond <<a href="mailto:jeff.science@gmail.com" class="">jeff.science@gmail.com</a>> wrote:<br class=""><br class="">TL;DR merge the repos.<br class=""><br class="">I honestly don’t know why any project would separate the test bucket from the implementation except strictly at the git repo level i.e. test bucket repo is assumed to be git submodule in implementation repo.<br class=""><br class="">Jeff<br class=""><br class="">On Fri, Aug 24, 2018 at 5:23 PM Hefty, Sean <<a href="mailto:sean.hefty@intel.com" class="">sean.hefty@intel.com</a>> wrote:<br class="">Because of the need to support OS and platform portability, there's a small, but growing, amount of code that needs to be shared between fabtests and libfabric. Today the code has been duplicated. (As an example, the definitions for complex data types are duplicated).<br class=""><br class="">I know git has a submodule option (and subtree) that's close to what we need. We might also be able to use some sort of build script to pull in the related files. We could even move the shared code into a separate repo used by both, which might make submodules friendlier, and is probably the 'right' choice...<br class=""><br class="">Does anyone have ideas as to the best option here?<br class=""><br class="">- Sean<br class="">_______________________________________________<br class="">ofiwg mailing list<br class=""><a href="mailto:ofiwg@lists.openfabrics.org" class="">ofiwg@lists.openfabrics.org</a><br class="">https://lists.openfabrics.org/mailman/listinfo/ofiwg<br class="">-- <br class="">Jeff Hammond<br class="">jeff.science@gmail.com<br class="">http://jeffhammond.github.io/<br class="">_______________________________________________<br class="">ofiwg mailing list<br class="">ofiwg@lists.openfabrics.org<br class="">https://lists.openfabrics.org/mailman/listinfo/ofiwg<br class=""></blockquote><br class=""><br class="">-- <br class="">Jeff Squyres<br class=""><a href="mailto:jsquyres@cisco.com" class="">jsquyres@cisco.com</a><br class=""><br class="">_______________________________________________<br class="">ofiwg mailing list<br class="">ofiwg@lists.openfabrics.org<br class="">https://lists.openfabrics.org/mailman/listinfo/ofiwg<br class=""></div></div></blockquote></div><br class=""></body></html>