StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>In my shop, we have many projects that are simply in separate repos, but the main application's repo has 2 other projects in it. One is a module that shares a significant amount of code with the main application, and the other is for database migrations for the application (it's even in a different language). I wanted related changes in both the application and the migrator to be committed together, inseparably. Altogether, all source files in this repo are between 10 and 11 MB.</p> <p>So if putting everything in one repository is really what makes sense because you don't want to deal with subrepositories, then there's nothing wrong with putting everything in one repository. The one of mine is on the small side of medium, in my opinion. TortoiseHg's source is around 20 MB, OGRE is over 100 MB.</p> <p>Without knowing more about your projects and their relationships, the impression I get is that a single repository would work just fine, and that you're not looking at this incorrectly.</p> <p>If you change your mind, <a href="http://mercurial.selenic.com/wiki/ConvertExtension" rel="nofollow"><code>hg convert</code></a> can help you extract projects into their own repository, maintaining the history of those files.</p> <p>If the one-repository approach is not for you, then I think <a href="http://mercurial.selenic.com/wiki/Subrepository?action=show&redirect=subrepos" rel="nofollow">subrepos</a> should be given a chance, as that is the only other method I know of for treating multiple repos cohesively that is supported in TortoiseHg (see the <a href="http://mercurial.selenic.com/wiki/Subrepository?action=show&redirect=subrepos#Recommendations" rel="nofollow">Recommendations</a> section).</p> <p><em>However, I'm not sure how you would deal with the inter-department access, given that it doesn't seem there is an established subset already shared with others.</em></p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload