3 ms·
One thing that submodules do better than subtrees is scale; in a subtree, everything is part of your repository (thus, index, and the associated problems with h
by beagle3 14y ago
One thing that submodules do better than subtrees is scale; in a subtree, everything is part of your repository (thus, index, and the associated problems with having having millions of files).
Submodules, on the other hand, have independent index files tied to independent repositories, so it's possible to not have a huge index anywhere regardless of total repository size.
- pixelcort 14y agoOne issue with submodules is if they rebase and GC out the commit you're pointing to, you're going to have a bad time. This may not be a problem when pointing to the commit of a stable tag, but when pointing to a development commit that might be rebased out later, you may find the submodule not to work. Not to mention if the server hosting the submodule is down and now all of a sudden you can't redeploy. One workaround is to fork the submodule and point to a commit in your fork.
- beagle3 14y agoBut that's basically not different than rebasing a public repo regardless of submodules or subtrees - all hell breaks loose