>One way to get the required information would be to use the information we get from the log. If we see >that the path that we are examining has got property changes in a revision, we could get the properties >and then specifically check for changes in svn:mergeinfo. Any changes to that propery would translate >to a merge operation performed in that revision.
>This would make the revision graph even slower, as we would need to fetch all property changes made >to a path, but I think it would be a possible solution. Or is there a smoother way to get at this >information?
As far as I can see we can get the required merge information by using the following SVN command
* SVN LOG -G -V -R X:Y * where X and y is a revision range involved.
The above command will fetch the history of each revisions along with its corresponding mergeinfo (if any). I tried
and attached the output file here.So I dont think so we should do log , check for Properitychanges or so.
So I am right now analysing TSVN Cache structure, Once it is known we can just store the collected data into the cache and retrieve it back for generating graphs.
1. First thing is that we should analyse how exactly the cache file is created from log and how can we
add data into that cache so that it is not breaking the backward compatibility. ( Must do some tweaks to CRootOutputStream or any class related to that) I am looking at that right now.
2. Once that is done, We need to study how the data is again retrieved from that cache file(Using Indexpairdictionary and revision index)