My recommendation is to learn these techniques anyway and try them out before deciding whether to use them or not.īeing spoiled with TortoiseHg workbench may mean never having been forced to do version control management from the command line. In Git it's common to rewrite history to clean up commits, while in Mercurial land rewriting history would be frowned upon. There are some philosophical differences to be aware of also. To enjoy using Git it is really important to take this seriously and spend the mental effort required to learn how Git works. Git is similar in many ways to Hg, but still quite different.
#Tortoisehg timing out when pulling free
My thinking was that since Git was so prevalent someone must have made a brilliant free GUI that will make everything obvious, so I wouldn't have to spend time and energy to learn the nitty gritty details of the Git command line. Stop looking for a GUI that matches TortoiseHg workbench.You may want to follow a Git getting started tutorial in parallel with reading this. Note that this is not written for total Git beginners.
There is no free GUI for Git that match the power and ease of use of TortoiseHg workbench, and some terms in Git just annoy hg users to no end, like what exactly a pull is supposed to do.īut there is hope, of course, and in this article I will explain key concepts that I found important to understand properly coming from Hg, and you will find some hints to make the Git experience more smooth. Using Git as an experienced hg / Mercurial user can be frustrating.
0 kommentar(er)
