It’s nice to know that there is this .git/info/grafts feature, which lets you join history between the repositories. This might, for example, be used in helping DragonFly BSD move sys/ out of the rest of the repo, whilst still preserving the history (and making sys a submodule).
Other than that, some advice in the article is quite contradictory to the principles of git, like rewriting the whole history with git filter-branch, which they present as having just “a minor drawback” of invalidating all the commit ids.
It’s nice to know that there is this
.git/info/graftsfeature, which lets you join history between the repositories. This might, for example, be used in helping DragonFly BSD movesys/out of the rest of the repo, whilst still preserving the history (and makingsysa submodule).Other than that, some advice in the article is quite contradictory to the principles of git, like rewriting the whole history with
git filter-branch, which they present as having just “a minor drawback” of invalidating all the commit ids.