![]() Now you do have the current version of command line Mercurial and the SVN convert tool, too. Installation is really easy: Download and install TortoiseHg and just one reboot. No more broken histories, because you have used your favourite renaming tool instead of 'svn move'. Afterwards choose the "Guess renames" feature in the context menu and have fun. And it still improves very fast (I used it since version 0.4, current is 0.9.2 with Mercurial 1.4.2).Ī nice feature for example: Just do a lot of refactoring in your IDE and don't care about renaming. If your familiar with TortoiseSVN you can use it straight away.Īs of today, TortoiseHg is better than TortoiseSVN in my opinion. You can even work with Git repositories using the hg-git extension for Mercurial, as CAD bloke mentions. Mercurial's Subversion import is also fantastic. There are a few quirks in the interface, but overall it's very solid (and if you use the revision graph view it looks great). It also installs the hg command-line system, so you can drop down into that if you need to (or if you prefer doing version control on the command line). I've personally had good experiences with TortoiseHg. ![]() And if you're used to using TortoiseSVN, the transition to Git should be pretty smooth, as TortoiseGit is based upon the TortoiseSVN code base and reuses a lot of it's UI and design principles. Of the three that you mentioned, Git certainly has the most polished "Tortoise", in my opinion. Whilst it's true that git's performance suffers on windows, it's going to be perfectly acceptable in most situations. I guess on some aspects Mercurial is still more centralised than Subversion.I've been using TortoiseGit for a while. Having all history in one dir and all ignore rules in one files seems a better approach to me. The end result is the same, but the way Mercurial handle it with one file is more appealing to me. On Subversion, I can add files to the ignore list so they don't show as "unversionned", but I can also add a svn:ignoreproperty to a specific directory to set regexp to files that I don't want to track. The syntax can be a little strange sometimes, it took me a while to correcly understand it, but it definitely works. I have some files in my project I don't want to track (like auto-generated cache files). Subversion will allow me to do a commit of one special feature by committing only one directory, but the TortoiseHg integration help me doing commits more easily no matter where I'm browsing. I can see the benefits of both and I'm not quite sure which is better. You have to add an empty file in each to allow tracking.Īlso, when doing a commit in a specific directory in Mercurial, it will commit the whole repo, while with Subversion it will only commit the current repo. Subversion can track empty directory, just by adding them. I really like the TortoiseHg vision better. It allows me the easily see what changes where made, and help me write my commit message. In TortoiseHg, all new files are automatically seen in the commit window, as well as a diff. If you added new files, they won't show unless the "Show unversionned files" is checked. When you commit with TortoiseSVN it displays the list of files that where updated since the last commit. I am using both TortoiseSVN and TortoiseHg. You do not have to deploy anything anywhere, just update your current repo with data from one of the revision. On the other hand, each Mercurial repository holds both the current public version and all the history. That revision do not hold any history information, it is only a copy of your project at a given time. Subversion is centralised while Mercurial is distributed.Īs far as I understand the difference, it means that Subversion uses one main directory to store the versionned version and can deploy (export) a specific revision at anytime. While the Subversion approach litters your app with countless hidden directories, making copy and pasting a real pain. hg directory to transform your versionned version into a stand-alone one. I prefer the Mercurial approach, it keeps all changes centralized in one place. svn directories in each directory, to track history changes to that directory only. hg directory at the root of your project to store all your project history while Subversion adds multiple. Here is a little list of changes, mostly as a reminder for myself. And moving from one to the other meant changing a lot of reflexs I had. ![]() I never used Subversion before, the only versionning system I ever used was Mercurial. People at my current job are using Subversion, and our project will be tracked using it. Differences between Mercurial and Subversion
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |