On 02/01/2012 08:46 AM, Johan Corveleyn wrote: > Perhaps this issue can be deferred if the API would allow you to get / > cache all the inheritable props, up to the repository root (since they > are always readable anyway, regardless of authz). Not only "up to the > nearest path-wise ancestor that has the property", but "give me > everything up to the root". Then the concrete consumer of the prop can > always add special syntax and corresponding inheritance / override / > append behavior specific to its uses (a special syntax that defines > how the multiple inherited props are to be "overlayed").
I've already expressed support for providing the raw(est) APIs and allowing
users to drive them as they see fit to interpret what is ultimately their
own custom properties, with custom meanings, custom syntaxes, etc.
We could even add an option ('svn propget --parents PROPNAME TARGET') which
would cause Subversion to print out those path/propval pairings all the way
up the tree to facilitate scripted usage.
--
C. Michael Pilato <cmpil...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
