Updating inheritable properties in publishing site partnersuche im internet kostenlos Ulm
For an exhaustive list of Subversion's predefined properties, see the section called “Subversion's Reserved Properties”.
presume thereafter the existence of those properties, and neither should you or the tools you use to interact with your repository.
Otherwise, you run the risk that a future release of Subversion will grow support for a feature or behavior driven by a property of the same name but with perhaps an entirely different interpretation. Just as files and directories may have arbitrary property names and values attached to them, each revision as a whole may have arbitrary properties attached to it.
The same constraints apply—human-readable names and anything-you-want binary values.
Generally speaking, the names and values of the properties can be whatever you want them to be, with the constraint that the names must contain only ASCII characters.
So, when writing scripts which operate on your Subversion repository data, do not make the mistake of assuming that any particular revision property exists on a revision.
You can modify, commit, and revert property changes as easily as you can file content changes.
And the sending and receiving of property changes occurs as part of your typical commit and update operations—you don't have to change your basic processes to accommodate them. While there are only a handful of such properties in use today, you should avoid creating custom properties for your own needs whose names begin with this prefix.
But it certainly leaves much to be desired in terms of both performance and likelihood of success, especially if the scope of your search would require a working copy from the root of your repository.
For this reason, you might choose—especially in the revision property use case—to simply add your metadata to the revision's log message using some policy-driven (and perhaps programmatically enforced) formatting that is designed to be quickly parsed from the output of But here again lies some misfortune.
While Subversion places few restrictions on the names and values you use for properties, it has not been designed to optimally carry large property values or large sets of properties on a given file or directory.