Geek Answers Handbook

What is the best way to review code through a few commits with TortoiseHg?

The problem I am facing is that I have several code reviews, with ~ 10 commits per view. This is an active repo with constant commits from developers. I have TortoiseHg that filters my changes, so I only look at the ones that concern me.

What I would like to see is the difference between the set of changes before the first change and the last (without displaying all changes unrelated to it). I just want to see the final results of all these changes. I don’t care that changeet 1 has some kind of horrible code that was fixed in 3. I just want to see the difference between what was eventually merged through all these changes.

It seems to me that I am missing the obvious, and this is not a vivid question. However, I still ask. Is anyone

+7
source share
2 answers

I am not sure about 1.1.8 since I am using version 1.9 / 2.0 release, but I believe that you can left-click on changeet1, right-click on revision 3 and select visual Diff. This should open your optional comparison tool and show only the difference between the two versions.

When I did this in a new turtle, he opened BeyondCompare in directory comparison mode, with revision1 on one side and revision2 on the other.

+3
source

Do not merge between commits and do not delete the clone of developers between start and completed change sets.

Or If merges have occurred, update and merge everything, and then take the entire code base (or just change the files) and upload it to a clean clone (make sure that you are working with the same version so as not to overwrite anything). Solve it all at once.

0
source

More articles:


All Articles