3 ms·
What are the actually serious downsides of having a repo for each project again? Serious question. Mercurial supports Subrepositories for example. Just define y
by EGreg 8y ago
What are the actually serious downsides of having a repo for each project again? Serious question. Mercurial supports Subrepositories for example. Just define your rules for pulling stuff.
From my own experience, if you are arguing about whether use convention A or convention B, the answer should be to have C that allows both, and then configurations on top of C for A and B.
This applies for example to lookups in the dabatase by an index.