![]() ![]() There are also a lot of UX problems with TortoiseHG that seem to originate in the design of Mercurial, though, so this may come down to my personal taste. (With everything else, even rewriting commands like git rebase, the reflog (see git help. First put your local changes in a patch file, then revert the changes in the working copy. Some recommend using the shelve extension or mq to handle that, but there is an even easier way. It is not possible to merge or rebase when there are uncommited local changes in the working copy. I'm not sure if this is because TortoiseHG is largely written in Python+QT, or just because TortoiseGit is more mature - I use TortoiseHG a lot at work when interacting with mercurial repositories, and it crashes frequently, but I've never had TortoiseGit crash or freeze on me. Theres built-in shelve functionality in TortoiseHG. Merge or rebase with uncommitted changes. TortoiseGit is also faster and more stable than TortoiseHG. That might make it easier to get used to working with Mercurial. It allows to perform many hg operations using the context menu and toolbar buttons. I've yet to find any equivalently pleasant user interfaces in TortoiseHG pretty much all of TortoiseHG's user interfaces are tangled messes of dropdown menus and checkboxes that try to reproduce every mercurial configuration switch. TortoiseHg is a multi-platform graphical user interface for Mercurial repositories. ![]() In particular, Rebase in TortoiseGit has an excellent user interface that takes Git's command line rebasing process and turns it into a user-friendly graphical equivalent. This is really good if you want to get work done without being a Git expert. In many cases it offers commands that encapsulate a set of underlying operations for example, TortoiseGit offers subversion-style Commit and Revert dialog boxes that behave like the equivalent dialog boxes in TortoiseSvn, even though Git has no directly analogous commands. If checked, Mercurial will try to resolve trivial merge conflicts without user. TortoiseGit's UI is much better designed than TortoiseHG's - operations you want to perform tend to be exposed in more obvious places, with clearer names and simpler UIs. If update or rebase are selected, a pull operation may result in a merge.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |