Tasks #2216
Consider using git subtrees instead of submodules
| Status: | New | Start date: | 04/02/2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | rsb-1.0 |
Description
We can all agree, that our submodule setup sucks.
We discussed and rejected gitslave: https://projects.cor-lab.org/projects/corcse/wiki/GitSlave
Nicolas Hafner suggests git subtrees, which I (jmoringe) did not know about. We should probably look into that possibility.
http://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-subtree/
History
#1 Updated by J. Wienke almost 8 years ago
Looks nice.
#2 Updated by J. Wienke almost 8 years ago
After locking at this I can say that this still does not solve the problem. A subtree is basically a complete or squashed inclusion of another repository at a certain directory inside a git repository. There is still no automatic tracking of the other repository. That means we would still have to manually update the inclusion and tell users commands to do these updates on their own. Moreover, since the other repositories are basically include in the top-level repository, the size of this repository will be much bigger. So I don't think this solves our problems.