Should .git of vendored packages be committed with the vendor folder?

<p>So I am trying to do manual vendoring in 1.5. I did git clone under my vendor directory and the compiler was able to find the package. Great!</p> <p>Now my question is, I want to commit the changes including the vendor folder. Should I include the .git of the vendored package or delete it and keep just the code + license?</p> <hr/>**评论：**<br/><br/>HectorJ: <pre><p>Git submodules are the way to go IMO.</p> <p>&#39;go get&#39; will now fetch them. </p> <p>Shameless plug : I&#39;ve been working on a tool to manage go1.5+ dependencies with the main objective of keeping packages &#34;naturally&#34; go-gettable with their pinpointed dependencies : <a href="https://github.com/hectorj/godm">https://github.com/hectorj/godm</a> </p></pre>rem7: <pre><p>I prefer using git subtrees and merging with --squash</p></pre>kylewolfe: <pre><p>Oh, nice! The issue for it is still open, so this slipped by without me noticing! (<a href="https://github.com/golang/go/issues/7764" rel="nofollow">https://github.com/golang/go/issues/7764</a>)</p></pre>peterbourgon: <pre><p>Strong -1. git submodules are broken by design; use subtrees, or copy manually.</p></pre>dlsniper: <pre><p>Sure, why not? It should be easier to upgrade them afterwards, no? And keep track of the differences between your version and the upstream version.</p></pre>reditter15: <pre><p>No.</p> <p>Having dependencies inside the repository is a good practice (some people may not agree), but the .git folder should not be commit, just the code.</p> <p>Godep does this for your in an automated way: <a href="https://github.com/tools/godep" rel="nofollow">https://github.com/tools/godep</a></p></pre>peterbourgon: <pre><p>This is probably the right answer.</p></pre>TheMerovius: <pre><p>If you include the .git, this will be converted to a git submodule automatically (I think) which is usually what you want.</p></pre>