"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
Later on I had to answer the question, betweeen which two releases a
1) With "svn log / Show Log" it was easy and fast to find the revision
2) The results of "Revision Graph" command were quite disappointing:
- it took several minutes (approx. 5) to retrieve the graph data. (Ok.
- In the graph I didn't find the previously researched revision number:
- There were many nodes in the main line of the graph, where the
- Later on, while testing with a separate repository, I found out (and
--- 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.orgReceived 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.