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

Re: Query on location segments report

From: David Glasser <glasser_at_davidglasser.net>
Date: 2007-12-24 20:48:57 CET

On Dec 24, 2007 6:02 AM, Kamesh Jayachandran <kamesh@collab.net> wrote:
> Hi All,
> I was trying to understand the 'get-location-segments' report.
> I have the following testcase(Sorry I don't have it in script form),
> please use the attached dump file.
> It is about keep renaming 'trunk' between each rename add one file in a
> different commit.
> a)load the dump
> b)Put a break point on
> 'subversion/libsvn_client/merge.c:normalize_merge_sources' just after
> the call to 'svn_client__repos_location_segments'.
> This gives the following segments
> segment[0] = {start_rev=1, end_rev=1, path="trunk"}
> segment[1] = {start_rev=2, end_rev=3, path=NULL}
> segment[2] = {start_rev=4, end_rev=5, path="trunk1"}
> segment[3] = {start_rev=6, end_rev=7, path="trunk2"}
> segment[4] = {start_rev=8, end_rev=9, path="trunk3"}
> segment[5] = {start_rev=10, end_rev=11, path="trunk4"}
> segment[6] = {start_rev=12, end_rev=13, path="trunk5"}
> I am concerned about 'segment[1]' why the 'path' is NULL as there is no
> gap in history.

It looks like there *is* a "gap": trunk1@4 is copied from trunk@1.
The commits at 2 and 3 don't affect the line of history that becomes

(Though I don't actually see anything in the docs for any of the
location segments function describing the "gap" segments; they're in
the code, though.)

btw, since dumps are binary files, I'd recommend attaching them
gzipped or something in the future.


David Glasser | glasser_at_davidglasser.net | http://www.davidglasser.net/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 24 20:49:07 2007

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.