Mergeinfo inheritance and mixed-rev WCs revisited

The Background:

The topic of mergeinfo inheritance within mixed-rev working copies was
first discussed here:

http://subversion.tigris.org/servlets/ReadMsg?listName=dev&msgNo=134295

In r28492 I made a change that prohibited inheritance across mixed-rev
boundaries.

Karl questioned the sanity of this change here,

http://subversion.tigris.org/servlets/ReadMsg?list=svn&msgNo=34070

and here,

http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=134338

-----

Karl,

Did you have a chance to think on this some more?

I'm somewhat ambivalent about taking working revisions into account
when doing mergeinfo inheritance. It is technically correct to do so
AFAICT, but in practical terms it is a headache whenever we have
mergeinfo anywhere other than branch roots. Worse I don't think
preventing inheritance across a mixed-rev path solves anything but
some far-out edge cases.

Isn't the larger issue about inheritable properties in general? They
are all fine and good in a WC with consistent working revisions. But
the moment mixed-revisions enter the picture we have to choose between
correctness and ease of use no?

Paul

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-01-25 17:13:28 CET