> -----Original Message-----
> From: Paul Burba [mailto:pburba@collab.net]
> Sent: Friday, October 05, 2007 12:25 PM
> To: Kamesh Jayachandran
> Cc: dev@subversion.tigris.org; Lieven Govaerts
> Subject: RE: svn commit: r26803 - in trunk/subversion:
> libsvn_client tests/cmdline
<snip>
> Summing up, at present I see two problems:
>
> 1) We have inconsistent start range notifications, sometimes
> the notification range represents the acutal merge being
> performed, sometimes it does not. Not sure how to spin that
> as other than a flaw :-(
>
> 2) Our notifications always show the merge target as the
> destination, even if the range in question is only being
> merged into one of the target's subtrees with differing
> mergeinfo. IMHO this is less serious, but does make for
> somewhat confusing outout.
Doh! We can probably scratch problem #2: If there are *two or more*
subtrees under the target which both need a given revision merged in,
then using the merge target in the notification is probably as good as
it gets.
Don't want to start listing *all* the subtree targets...or do we?
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 5 18:50:15 2007