> And, Git subtree is essentially the strategy m-c uses today: one large > repository holding the history (albeit sometimes squashed landings) of > many external ones.
however it has the possible advantage that the VCS has some idea what is happening, and you have the history for the external project. > If we switched to Mercurial subrepos and wished for Git to flatten these > subrepos into 1 large one, this is a feature hg-git would need to grow. > It's doable, sure. However, going from squashed Git back to Mercurial > subrepos could be problematic to say the least. I'm not sure it could be > done reliably. This may kill our idea to have a *fully* writable Git > server someday (we may need to prevent writes to directories that are > Mercurial subrepos). http://khuey.pastebin.mozilla.org/2253745 seems to demonstrate that at least in theory it is possible to extract a history for the sub project and push just that history somewhere, but the integration foo seems non trivial. > At the point you are squashing repos into 1 to convenience Git, you > might as well do the same to Mercurial to facilitate easier conversion. having useful blaim in the main repo may or not be a significant advantage Trev > That leaves us pretty much with where we are today. > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
