On Thu, 28 Apr 2005, Fabien COELHO wrote:
> > Perhaps a better solution might be to check the property names in the
> > pre-commit hook to make sure they're valid svn properties?
>
> That has been suggested, but I feel it is too strong and too late:
>
> you cannot just send a warning from pre-commit, you can only abort the
> commit, so there would be no way to put a non standard svn:* property,
> which would be bad: for instance, I could use the old svn and set up the
> repos for some new upcoming props (e.g. svn:need-lock) before the repos
> soft is actually upgraded.
>
But if you have it in the pre-commit hook, then it is a repository policy.
If you are going to set svn:needs-lock, you just add that to the hook.
And you can add your own private properties as well.
> The "reserved" stuff is more a suggestion on which I have no real
> technical opinion.
>
NOte that svn: properties *are* reserved; don't use it for your private
needs.
> >From the implementation point of view, it is quite simple to implement
> that in a client, but having the list of set properties with svnlook from
> within pre-commit does not look that easy.
>
>
Doesn't svnlook diff show property mods?
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Apr 28 20:10:19 2005