jklowden_at_schemamania.org writes:
> In svn_subst_build_keywords2, no message is produced if a token in
> keywords_val has no meaning to svn:keywords. The result is that mispelled
> or mis-delimited keywords are silently ignored, leading to mysterious
> behavior.
>
> For example, the command:
>
> svn propset svn:keywords Date,Revision,Author,HeadURL,Id *.cpp
>
> (which conforms to common Unix command-line syntax for multi-valued
> options) is accepted, but has no effect. The user either doesn't notice,
> or wonders whether the feature really works as advertized.
>
> Although properties in general are just key-value pairs with no meaning to
> Subversion, a property that Subversion interprets does of course have
> a valid domain. The proper course when evaluating any input is to either
> accept or reject it, not simply to ignore it and let the user puzzle it out.
>
> Ideally this validation would happen when the property is being stored.
> I think perhaps the best place would be svn_wc_prop_set2.
>
> As a second suggestion, it would be nice if the above syntax were supported.
> AFAICT the only coding change would be the constant string passed to
> svn_cstring_split in svn_subst_build_keywords2.
Completely agree with everything you say above.
> Would you like me to file a bug report?
Well, only if you haven't time to post a patch... :-)
http://subversion.tigris.org/hacking.html#patches
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-06-24 21:42:32 CEST