[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: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Mon, 17 Oct 2016 12:12:41 +0000

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. This way, if
a parent dir sets «*.txt = k1=v1», then a subdir can set «*.txt = k2=v2»
to get both k1 and k2 set, or can set «*.txt = k1;k2=v2» to have k2 set
and k1 unset.

I'm not sure whether this should be considered hacky (fixes one lacuna
by taking advantage of another) or effective (plugs two lacunas with one
stone).

Cheers,

Daniel

P.S. The design document for inherited props, the unit tests, and the
book all use precisely the same example.
Received on 2016-10-17 14:14:37 CEST

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