> | The revision graph as it is structured today is almost useless for me.
>
> Then don't use it!
That's what I do :-)
>
> | And still I think it would be possible to structure the revision graph
> | in a similiar way allthough it's not the same as the version tree.
> |
> | But it might be that others are using it differently.
>
> * merge lines are not possible to show in the graph because Subversion
> doesn't provide that information (at least not in a way that takes less
> than a week to fetch it from the repository)
> * have you tried the 1.5.0-beta1 release yet? The graph looks very
> different there than in 1.4.x versions
I had a look at it. It looks much better but for me it's still hard to
get an overview.
Perhaps I'll get used to it when we use the new version when it is
released.
> * Seems ClearCase 'optimizes' the graph to get the shortest lines
> possible. You can do that with small repositories. If you however try
> that with a really big repository (try the KDE one), you would have to
> wait *hours* for such a graph to show. I don't know if ClearCase can
> even handle such repositories...
ClearCase has a different branching concept. A new version only
appears on a branch when you have changed it on that branch.
This is where the difference between revisions and versions appears.
Ralf
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-04-03 12:24:56 CEST