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

RE: Server side svn:auto-props, how to set it correctly?

From: Bo Berglund <bo.berglund_at_gmail.com>
Date: Sun, 18 Feb 2018 14:56:58 +0100

>>>> editor pops up and I enter all of the lines like:
>>>> *.c = svn:eol-style=native
>>>> *.cpp = svn:eol-style=native
>> Do I also have to handle case here?
>> I.e. for each file pattern do I have to figure out all case
>> permutations too?
>> Ex:
>> *.cpp = svn:eol-style=native
>> *.cpP = svn:eol-style=native
>> *.cPp = svn:eol-style=native
>> *.cPP = svn:eol-style=native
>> *.Cpp = svn:eol-style=native
>> *.CpP = svn:eol-style=native
>> *.CPp = svn:eol-style=native
>> *.CPP = svn:eol-style=native
>>
>> Or is it just the svn_apply_autoprops.py that uses case sensitive
>> pattern recognition?
>> I noticed a file not getting the property set when I used it...
>> It was named in all caps.
>
>Paths in Subversion are case-sensitive. All patterns are case-sensitive
>too. You'll either have to add all case permutations, as you showed
>above, or teach your users some discipline in naming files.

OK, I see.
But I have an additional clarification question:

In my local .subversion/config file (on Windows) I have this comment in
the auto-props section. BTW it is the same on an Ubuntu machine:

[auto-props]
### The format of the entries is:
### file-name-pattern = propname[=value][;propname[=value]...]
### The file-name-pattern can contain wildcards (such as '*' and
### '?'). All entries which match (case-insensitively) will be <<==
### applied to the file. Note that auto-props functionality
### must be enabled, which is typically done by setting the
### 'enable-auto-props' option.

To me this indicates that the auto-props patterns are case-insensitive.
Or is this a old artifact that has not been updated since it is just a comment?

Or maybe the server side auto-props are case sensitive while the client side is not?

PS:
I usually communicate with this list via the Gmane news mirror, but today I
have found that the gmane.org domain itself seems to have vanished from the Internet!
Too bad if this is not a temporary issue.
Looks not so good if the DNS name disappears rather than the server not responding.
DS
Received on 2018-02-18 14:57:08 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.