<div dir="ltr">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><br></div><div><a href="https://codingkilledthecat.wordpress.com/2012/04/28/why-your-company-shouldnt-use-git-submodules/">https://codingkilledthecat.wordpress.com/2012/04/28/why-your-company-shouldnt-use-git-submodules/</a><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 7, 2016 at 1:10 AM, Max Howell <span dir="ltr"><<a href="mailto:max.howell@apple.com" target="_blank">max.howell@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Another option that has occurred to me after talking with Tim Kientzle is to use <b>git submodules</b><div><br></div><div>submodules lock other clones to a specific revision. Our Packages/ directory is already a directory of clones.</div><div><br></div><div>I have not given it a lot of thought yet, but there is possibly power in reusing this existing part of git.</div><div><br></div><div>Mailed here for input.</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Ankit<br><br></div>
</div>