[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn:auto-props: property specified in a parent dir but not specified in a subdir

From: Stefan <luke1410_at_posteo.de>
Date: Tue, 18 Oct 2016 09:32:04 +0200

On 10/17/2016 15:37, Branko Čibej wrote:
> On 17.10.2016 14:12, Daniel Shahaf wrote:
>> Johan Corveleyn wrote on Mon, Oct 17, 2016 at 10:18:35 +0200:
>>> Omitting the '=' also doesn't cut it:
>>>
>>> [[[
>>> C:\autoprops\wc\trunk\dir>svn pg svn:auto-props --show-inherited-props
>>> C:\autoprops\wc - *.txt = svn:eol-style=native
>>>
>>> C:\autoprops\wc\trunk - *.txt =
>>> svn:eol-style;svn:mime-type=application/octet-stream
>>>
>>> C:\autoprops\wc\trunk\dir>svn add test.txt
>>> svn: E135001: Unrecognized line ending style '' for
>>> 'C:\autoprops\wc\trunk\dir\test.txt'
>>> ]]]
>> Quoting ~/.subversion/config:
>>
>> [auto-props]
>> ### The format of the entries is:
>> ### file-name-pattern = propname[=value][;propname[=value]...]
>>
>> So the «=value» part is allowed to be omitted entirely, but what are the
>> semantics of that? They don't seem to be documented.
>>
>> It seems to me that we can *define* that if the = sign is absent, then
>> the value of the property will be not "" but NULL.
> Unfortunately the implementation
> (libsvn_client/add.c:all_auto_props_collector()) already explicitly
> handles 'propname' as if it were 'propname=', i.e., sets the value to
> "". Since the "documentation" in the generated config file already
> implies that the '=' can be absend, I'd say this behaviour is pretty
> much set in stone.
>
>
> -- Brane

From a user's point of view I'm also not sure whether a syntax of *.foo
= k1 would be intuitive to read as if that's unsetting the property...
Personally I wouldn't get that behavior tbh, without reading the
documentation.

Regards,
Stefan

Received on 2016-10-18 09:32:14 CEST

This is an archived mail posted to the Subversion Dev mailing list.