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

"revision graph": unexpected behaviour/display result.

From: Kuno Meyer <kuno.meyer_at_gmx.ch>
Date: 2006-08-27 12:10:09 CEST

Hi all

(Working with TSVN 1.3.5)

Lately we have migrated a moderately large CVS repository to SVN (3000
revs, 800 MB disk size, served by apache over http protocol).

Later on I had to answer the question, betweeen which two releases a
specific change in a specific file had been made.

1) With "svn log / Show Log" it was easy and fast to find the revision
number and the time of the change. But for which release was it?

2) The results of "Revision Graph" command were quite disappointing:

- it took several minutes (approx. 5) to retrieve the graph data. (Ok.
that's a known issue / limitation of SVN, and my mail is not mainly
about this point)

- In the graph I didn't find the previously researched revision number:
I didn't notice that only branch points are displayed (Perhaps due to
the wording "revision", which means for me every revision, not only
branch points)

- There were many nodes in the main line of the graph, where the
underlying file didn't change. (For example I get a node for every
branch operation, even when the underlying file remained untouched
between those two revisions. This greatly increases the complexity of
the displayed image, therefore hiding the important information)

- Later on, while testing with a separate repository, I found out (and
was quite surprised) that I couldn't generate a revision graph for a
file that wasn't yet involved in a branch operation.

---
OK. To come to an end: My *proposal* for improving the revision graph:
1 (Option A): Rename the command to "Branching graph" instead of 
"revision graph".
1 (Option B): Leave the wording at "Revision graph", but display all 
changes, not only the branch points
2 (both A+B): Do not display several branch nodes / revision nodes, when 
the underlying file hasn't changed. This means that a single "file 
revision" can be the source of multiple copy/branch/tag operations.
(If you know the "revision graph" feature of WinCVS, then you probably 
understand what I want to say.)
---
With kind regards
Kuno Meyer
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Aug 27 15:41:18 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.

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