Diff tool is useless in all but the simplest of scenarios

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
gsmalter
Posts: 115
Joined: Sat Jul 09, 2005 11:13 am

Diff tool is useless in all but the simplest of scenarios

Post by gsmalter » Mon May 12, 2008 10:12 pm

We use Vault to create a recursive diff list comparing the last labeled inspection to the current code. This works great. We get a list of files that are Different, and ones that are Right Only, Left Only.

The lines in the diff list that are Different are great. We can double click on them to see a diff of the last inspected version and the current version. The diff tool itself is great.

For Right and Left Only files, double clicking does nothing. If we want to diff the file, we have to find it manually in the client or in visual studio and do a history. This is inconvenient.

Worse, if a file is Left Only it means you deleted it, renamed it, or moved it. If a file is Right Only it means you added a brand new file, renamed it, or moved it. Not distinguishing between these is a big drawback.

Basically, if you ever move or rename a file, you a screwed when it comes to diffing. Even though Vault is smart enough to deal with files on an ID basis, the diff tool seems to use a straight up string comparison and has no idea that the file with the old name is in any way related to the same file with the new name.

It would be nice if diffing was resistant to moves and renames, and still let us double click on the row and see a diff.
Vault 5.0, Visual Studio 2010, Enhanced Client

jeffhostetler
Posts: 534
Joined: Tue Jun 05, 2007 11:37 am
Location: SourceGear
Contact:

You are right. That is a problem.

Post by jeffhostetler » Tue May 13, 2008 6:48 am

You are right. That is a problem. I guess I never really thought
about it from the context you've described.

And yes, the diff tool is using a straight string compare on the
relative pathnames.

Let me log a bug on this and see if we can't improve the situation.

Sorry,
jeff

Post Reply