David Glasser wrote:
> On Dec 12, 2007 11:23 PM, Kamesh Jayachandran <kamesh@collab.net> wrote:
>
>>> (One big question I'm concerned about, looking at that API, is peg-rev
>>> resolution. What if "merge_target" refers to different, unrelated
>>> lines of history at min_commit_rev and max_commit_rev?)
>>>
>>>
>>>
>> Caller subversion/libsvn_client/merge.c filter_reflected_revisions does
>> a peg rev lookup and calls the API with relevant paths and revisions.
>>
>
> Are you saying it *should* do that or that it does? I don't see that now.
>
> --dave
>
>
It does that, revision number and urls are normalized via
normalize_merge_sources early in the call chain.
With regards
Kamesh Jayachandran
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 13 09:54:05 2007