We came to the same conclusion when we built the revision graph in Subclipse back in 1.5:
http://subclipse.tigris.org/graph.html Trying to do log on a whole branch with -g could even get quadratic loops and take forever. Doing it one revision at a time was the only thing that would work but then it does not perform. At the time, something I had asked for was a way to get run log on a branch and get a boolean for every revision where mergeinfo changed so that we could then just follow up and ask for those revisions. A better solution as Philip suggests would be even better. Mark On Wed, Mar 26, 2014 at 3:15 PM, Henrik Carlqvist <h...@poolhem.se> wrote: > I have written a tool, svn2cvsgraph > ( http://svn2cvsgraph.sourceforge.net/ ) > to graphically display svn revision graphs. > > Since version 1.6.17 of svn, "svn log -g" no longer shows any merges when > examining the repository root. After a discussion, here > http://svn.haxx.se/users/archive-2013-12/0029.shtml > I rewrote svn2cvsgraph to not only do "svn log -g" on the repository root, > but for trunk and every branch in the repository. > > After releasing that new version of svn2cvsgraph I found that some merge > information is missing from svn versions newer than 1.6.17 even when > examining each branch. I filed an issue about this (issue 4477). > > I could once again rewrite svn2cvsgraph to also work with newer versions > of svn. The solution would be to make one call to "svn log -g" not only > for each branch but for every revision. I have done some internal testing > with this approach and the C code for svn2cvsgraph looks nice and clean, > but I still hesitate to make such a version of svn2cvsgraph public. > > Would people hosting public svn repositories think that it would be nice > if some people using my tool would make one svn connection for each > revision in the repository? > > regards Henrik > -- Thanks Mark Phippard http://markphip.blogspot.com/