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

Re: svn commit: r27431 - trunk/subversion/libsvn_client

From: Karl Fogel <kfogel_at_red-bean.com>
Date: 2007-10-27 00:49:36 CEST

cmpilato@tigris.org writes:
> More work in issue #2953. Change the way merge source normalization
> happens to account for the annoyance that given a segment of path FOO
> and revision coverage from N to M (inclusive), you can't actually do
> anything useful unless you expand the range to N-1 (exclusive) to M
> (inclusive), and path location for N-1 (which might not be FOO, but
> perhaps is whatever FOO was copied from in rN).

I realize I'm stepping into a hornet's nest of complexity, but how is

    N(inclusive)-->M(inclusive)

different from

    (N-1)(exclusive)-->M(inclusive)

...in an algebra following the normal rules?

Also, I didn't understand how the last clause of the last sentence
above fits in. Is a verb phrase missing or something?

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 27 00:49:49 2007

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