Escolar Documentos
Profissional Documentos
Cultura Documentos
In addition, try to do this scenario on your laptop while not connected to the Internet. With Git/HG, no
issues, the repository is local; however, with Subversion, you’re out of luck. Your new branches will
have to wait. The advantages of Git/HG for branching are clear in this simple branching scenario.
Both Mercurial and Git communities are working on TortoiseHg/TortoiseGit types of GUIs for Windows
users. Git appears to have a sane Windows port now as well.
For most uses, Mercurial and Git are more-or-less interchangeable, especially with the usability
improvements in versions 1.5 of Git and later. The most basic commands like status, diff, commit, and
log behave very similarly (at first glance). Commands execute quickly, even for large trees. Both
systems are very flexible with modules and scripts that bring most features to parity. For myself,
having learned how to work with Git, I prefer the power Git offers with fast branches and powerful tools
like reflogs and rebase. For the undecided, fortunately there are tools that convert repositories from
Git to Mercurial and vice-versa, so other than mental switching costs, there is little to fear in choosing
one or the other. I won’t be using Subversion or CVS any more if I can help it.
In conclusion, GIT or Mergurial(HG) stands out far better, robust and built keeping the requirement of
new breed of programmers and collaborated development environment in mind. And SVN is slowly
outdating. Now, please read this article to understand where GIT and Mercurial stands at this point.
http://texagon.blogspot.com/2008/02/use-mercurial-you-git.html