subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nico Kadel-Garcia <nka...@gmail.com>
Subject Re: Server side svn:auto-props, how to set it correctly?
Date Mon, 19 Feb 2018 01:29:05 GMT
On Sun, Feb 18, 2018 at 8:56 AM, Bo Berglund <bo.berglund@gmail.com> wrote:
>>>>> 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

> 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

Yes, it is. *Life* is case sensitive. Personally, I'd be startled to
see mixed case in a three-letter suffix, But Subversion is, in many
ways, based on CVS, which was originally written for UNIX and was,
indeed, case sensitive in file name handling. So I'm not surprised at
all by this.

Mime
View raw message