2 ms·
It's a win for DVCS in general, not just Hg. A couple of use cases off the top of my head: * I can take my repository on the train/bus/wherever and still commi
by anthonyb 17y ago
It's a win for DVCS in general, not just Hg. A couple of use cases off the top of my head:
* I can take my repository on the train/bus/wherever and still commit.
* If I'm working with someone who needs to use my 'buggy' code I can push just to their repository (or they can pull from mine).
* I can have my own workflow and create as many branches, checkouts, etc. as I need.
Of course, the example that he gives there is bizarre - effectively the Hg equivalent of hanging onto your code for 6 weeks and then merging all at once...
- nkassis 17y ago2 and 3 are easily done in SVN also. 2 is basically merging your changes in personal branch to the personal branch of another user. 3. Well your branch in SVN is your domain, do what you want. I think the main advantage is really for larger groups. Having 3000 branches in the linux repo would be unmanageable. Also, private branches are something SVN can't do to my knowledge. If I want to hack on a git repo without anyone knowing, it's easy. But there's many advantages to GIT/Mercurial over SVN/* aside from the "everyone has a repo". I love git but currently use SVN due to legacy and keyword expansion at work and it's not that bad.