Thanks for the reply. I actually planned on modifying the source of CVSGraph (which apparently does the same thing as WinCVS) to include all of the files in one graph. That turned out to be more work than it was worth, as laying out the structure for a single file is fairly trivial, and if I coded it myself, it would be easier to come up with my own representation.
I was looking for more of an idea for a comparison algorithm that works without specific revision numbers, as they are inconsistent across files. The only idea I have come up with as of yet is a list of branches which came before and after a specific branch, and use that information to place it in its proper position. I'm worried that this information may not be enough to ensure correctness. Thanks again. _______________________________________________ Info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
