On 10-07-23 09:20 PM, Avery Pennarun wrote: > > I'm pushing extra hard on this because I believe there are lots of > opportunities to just improve git performance on huge repositories. > And if the only *real* reason people need to split repositories is > that performance goes down, then that's fixable, and you may need > neither git-submodule nor git-subtree. I think I should mention one aspect of what we're doing, which is that a lot of our submodules are based on external code, and that we occasionally need to modify or customize some of that code. So it's quite nice for us to maintain private git mirrors of the external repos, with our own private branches that contain our modifications. Although we want to get much of our changes incorporated into the upstream code bases, upstream release cycles are rarely in sync with ours. So it's very convenient for use to have our external-code modifications contained in private branches in our private mirrors, and to rebase those branches to keep up with upstream releases. We also often use these private branches to maintain the code that integrates the external code bases into our overall build system. I mention this purely because this pattern is so convenient that I don't want to see it get lost in whatever may arise from this discussion. M. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html