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

issue-2987 branch: pegrev behavior for svn_fs_get_commit_and_merge_ranges

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

Kamesh: what is the peg/copy behavior for
svn_fs_get_commit_and_merge_ranges supposed to be (for the merge
target)?

(a) If the target is deleted and created in an unrelated way between
the beginning and end of the range, shouldn't it just return
information about the pegged version?

(b) If the target is copied from somewhere else during the range,
should it follow the copy backwards and given information about the
earlier version of the path?

I'm pretty sure (a) should be true but isn't (and since there's no
deletion in the sqlite schema, can't be until we fix that or use an
in-FS way of getting the information). Not sure what the right answer
ought to be for (b).

--dave

-- 
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 21:01:34 2007

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