I know that sub-repositories save you an your team time, but what is the ROI on them?
相关问题
- Mercurial compared to private branches in SVN
- How to abandon all Mercurial changes that haven
- Windows permissions on a directory: Mercurial - hg
- hg shelve installed but hg: unknown command 'u
- Reverting “discard all changes” merge effect
相关文章
- Mercurial Commit Charts / Graphs [closed]
- What is the tortoisehg gui equivalent of doing “hg
- How to use Mercurial from Visual Studio 2010?
- Is there a version control system abstraction for
- Mercurial discard local changes of a file or group
- Mercurial .hgignore Negative Lookahead
- How to see a mercurial difference
- Commiting Mercurial (Hg) branch to GitHub
If you have a dependency which is developed by you along with the main project then subrepos are a perfect fit IMO. I've been using subrepos in these circumstances for a while now and they save a lot of effort. I feel they're particularly beneficial for open-source projects, where getting all dependencies required to build your project can be a pain for someone checking out the code for the firs time: subrepos make this completely automatic.
I can't comment on how easy subrepos are to use if your dependency has its own separate distinct releases and/or is developed by a third party.