[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svn2cvsgraph, how to best handle merges?

From: Henrik Carlqvist <hc94_at_poolhem.se>
Date: Wed, 26 Mar 2014 20:15:40 +0100

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
Received on 2014-03-26 20:16:29 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.