![]() REAL programmers can make it do whatever they need it to.” But that’s the wrong perspective. ![]() The Git fanboys will try to play this off as a feature - “If you don’t like Git, it’s because you aren’t an expert. Mercurial+TortoiseHG just works.Īnd that’s the key. The point of VCS is to facilitate other work - the moment it starts feeling like actual work is a problem. Now launch TortoiseHg and select a change-set, right click any non-binary file in the change-set and select Diff to parent. If TortoiseHg has been running this whole time, shut it down. SourceTree, at least, will let you define custom commands so you can hack a directory diff shortcut together - but that shouldn’t be necessary! It’s one of those things that should just work. In the tortoisehg section, set the value of vdiff to vsDiffMerge. And none of them facilitate that basic concept I mentioned before- diff-ing the codebase at two arbitrary points in time. The GUI that comes with Git doesn’t even have the graph on the main window. But all of them seem to demote the graph view to a second class citizen. There are a plethora of Git GUIs out there (Sourcetree and GitKraken, for example). Making the graph the central part of how we interact with the repository makes sense, because it is the nearest we can get to its “true nature.”Įverything you can do directly from the graph in TortoiseHG On the metaphysical level, the repository is a history of how the codebase has evolved. When you are trying to bisect a bug, that time adds up. Try doing that on the command line- it would take a couple of minutes at least, assuming you have a directory diff tool already set up. Want to diff the entire codebase from 6 months ago to the current head ? You can do it in two clicks. are all seamlessly integrated into the graph. But what TortoiseHG does is make this graph central to the workflow - merging, diff-ing, branching, etc. So far, this is true of both Mercurial and Git. This means that the repository history can be viewed as a directed graph. The difference between Mercurial/Git and older VCS systems is the concept of changesets - each commit represents a set of changes to the code.
0 Comments
Leave a Reply. |