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

Re: Version tree

From: Branko Čibej <brane_at_xbc.nu>
Date: 2002-07-25 03:17:12 CEST

Marcus Comstedt wrote:

>"Henrik Svensson" <innotron@telia.com> writes:
>>Something like that. I would like to be able to make a graphical
>>representation of the file versions like
>>f . WinCVS also have a possibility to show a graph. I guess that i can do
>>some parsing of the log but that seems to be a bit primitive.
>Just looking at that picture and guessing what it means, it looks to
>me like you need to know three things to build it:
>* For the round "version" nodes: Which revisions in which the file
> has changed (easy).
>* For the square "branch" nodes: Which revisions of the file that
> have been copied/moved to other pathnames (and which those pathnames
> are). This seems to be more difficult. There is a "copyfrom_path"
> and a "copyfrom_rev" attribute in the log that gives the necessary
> info, although it points the wrong way. That can be fixed by
> requesting the entire log and reversing the links yourself of
> course. What's worse is that these attributes only seems to be
> added for moves, not for copies. Is that correct?

All of this information is available in the repsitory. Our new schema
was designed (in part) with exactly such functionality in mind. You'd
need some help from the server to get the required data, but it's be
much faster (and more accurate) than parsing the logs.

>* For the red "merge" arcs: Which revisions of the file that have
> been merged into another path, and what path and revision it has
> been merged with. Does svn merge record any relationship between
> the two merged files at all?

Not yet. Poat-1.0. Unfortunately.

Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 25 03:17:45 2002

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

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