<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><span class=""><div class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class="">I think git submodules can be added as an additional feature rather than depending on it completely for locking because it is a bit problematic to use with a team and has many issues<div class=""><br class=""></div><div class=""><a href="https://codingkilledthecat.wordpress.com/2012/04/28/why-your-company-shouldnt-use-git-submodules/" target="_blank" class="">https://codingkilledthecat.wordpress.com/2012/04/28/why-your-company-shouldnt-use-git-submodules/</a><br class=""></div></div></div></blockquote><br class=""></div></span><div class="">All the issues in the article are addressed by wrapping git with another tool, which we would do.</div><br class=""></div></blockquote></div><br class="">Can you elaborate "wrapping git with another tool" ? </div></div></div></blockquote><br class=""></div><div>`swift build` wraps git. All the pain points in that article are due to a lack of automation for various git-steps.</div><br class=""></body></html>