Re: Revision/History Graph - DAG (Directed Acyclic Graph)

Tue, 1 May 2012 09:21:39 +0200, /Thorsten Schöning/:
> Guten Tag Stanimir Stamenkov,
> am Dienstag, 1. Mai 2012 um 01:14 schrieben Sie:
>
>> Is anyone aware of tools which (re)construct a DAG from Subversion
>> repository history and display it pretty much like today's DVCSes?
>
> Did you already look at the revision graph e.g. TortoiseSVN is able to
> produce? From my point of view there's no real difference or are you
> missing any information? I don't knwo how merge tracking info is
> included because my Subversion serve ris still at 1.4.x.
>
> http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-revgraph.html

Yes, I've already had a look at TortoiseSVN, Subclipse, Subversive,
SvnMapper, svn-graph-branches and Syncro SVN Client:

http://tortoisesvn.tigris.org/bigpicture.html
http://subclipse.tigris.org/graph.html
http://www.eclipse.org/subversive/documentation/teamSupport/revision_graph.php
http://svnmapper.tigris.org/
http://code.google.com/p/svn-graph-branches/
http://www.syncrosvnclient.com/revision_graph.html

None of these resemble the DVCS examples I've given. All of these
require too much of visual space to describe just a little bit of
history with the valuable copy/branch and merge information. SVN
1.4.x is out of question as the merge-info is too important to omit.

If you're still wondering what I'm after, look at the Subversive
History view using merge-info (svn log --use-merge-history):

http://www.eclipse.org/subversive/documentation/teamSupport/history_view.php

Then map this to the examples I've already given:

http://code.google.com/a/eclipselabs.org/p/mercurialeclipse/source/list?r=ee7ed7ec51606117613924d0662fc03086787450

https://bitbucket.org/tortoisehg/thg/changesets/9fbf6b7fe9d5

Andreas Krey suggested nice approach in his reply - convert the SVN
repository to Git, then use that to display the history. I haven't
tried the SVN to Git conversion -- this is basically the only thing
I haven't tried yet, but I've tried SVN to Mercurial using various
tools available for the task, and in my experience this conversion
is far from perfect, especially with "weird" repositories. That's
why I'm searching for "native" SVN solution which takes as much of
the Subversion quirks as it could to reconstruct the history as nice
DAG which could be displayed pretty much like today's DVCSes can.

-- 
Stanimir