<div dir="ltr">I looked into git-subtree, and as I recall it, nothing in the setup recalls what subtree is used for what. Every git-subtree command you enter has to be fully explicit, which is a big hassle. Whereas git-submodule saves its state in the repository, so it knows what it's being used for and you only need to do it once. Hopefully I misunderstood git-subtree, but if I didn't, I found its interface disappointing.<br> </div><div class="gmail_extra"><br clear="all"><div>Carl Eastlund</div> <br><br><div class="gmail_quote">On Tue, Jul 30, 2013 at 5:41 PM, Asumu Takikawa <span dir="ltr"><<a href="mailto:asumu@ccs.neu.edu" target="_blank">asumu@ccs.neu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class="im">On 2013-07-27 07:10:54 -0600, Matthew Flatt wrote:<br> > I'm still unsure that submodules are going to be useful for managing a<br> > kind of "main-distribution" repository with references to package<br> > repositories.<br> <br> </div>Perhaps it would be worth considering using the git subtree feature<br> instead of submodules for the rest of the repository (just to clarify,<br> I'm not saying we should reconsider submodules for native-pkgs).<br> <br> Description here:<br> <br> <a href="https://github.com/apenwarr/git-subtree/blob/master/git-subtree.txt" target="_blank">https://github.com/apenwarr/git-subtree/blob/master/git-subtree.txt</a><br> <br> In particular, this aspect seems useful for us:<br> "you can also extract the entire history of a subdirectory from<br> your project and make it into a standalone project"<br> <br>