Johan Corveleyn wrote on Fri, Jan 06, 2012 at 13:16:06 +0100: > Come to think of it: using properties has the nice advantage that > these "configurations" come along when a project is branched or > tagged. Which is what most users would expect, I guess. > > If using some other server-side configuration mechanism, we'll surely > have to provide some wildcard support to be able to set a > configuration on a certain subtree *and all its branches and tags* > (and even then, this isn't the same as taking the configuration with > you to a new branch).
Another option would be to define a configuration for, say, the /trunk fspath, and when checking out a branch trace back through copies/renames to find this. This requires the 'branch root' concept (which Julian started on at some point). The configuration would then be maintained for /subversion/trunk and all branches would automagically inherit it too. It could either physically walk history (svn_ra_get_location_segments()) or shortcut and use the created path (FSFS cpath node-rev attribute) as the index to look up. Daniel (and yes, the latter would break up if /trunk@50 and /trunk@100 are not related...)
