You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Kelley T-Freytag <kf...@fnal.gov> on 2006/06/13 17:28:17 UTC
Problem with auto-props patterns
I am trying to automatically set a svn property on a file
called scu.exe. I want the property set regardless of
the case of the file name, e.g both scu.exe and SCU.EXE.
Putting scu.exe in the config file catches the lower case only.
Putting something like [Ss][Cc][Uu].[Ee][Xx][Ee] doesn't work
at all. If I have both :
scu.exe : svn:executable
SCU.EXE : svn:executable
in the config file, it will only attach the property on
the first definition it comes across: in other words, for
the example above filenames in lowercase are set but upper
case are not; and if you switch the order (put the upper
case first in the file) then it attaches the property only
on the upper case file.
Obviously, from the documentation, the * regular expression
wild-card works. What other regular expressions work? Why
doesn't 2 different names work?
Using svn: 1.2.1 on Linux,
1.3 on Windows
and am seeing the same behavior on both.
Thanks,
Kelley Trombly-Freytag
Fermi Nation Accelerator Laboratory
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Problem with auto-props patterns
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Jun 13, 2006, at 20:40, Garrett Rooney wrote:
> On 6/13/06, Kelley T-Freytag <kf...@fnal.gov> wrote:
>> I am trying to automatically set a svn property on a file
>> called scu.exe. I want the property set regardless of
>> the case of the file name, e.g both scu.exe and SCU.EXE.
>> Putting scu.exe in the config file catches the lower case only.
>> Putting something like [Ss][Cc][Uu].[Ee][Xx][Ee] doesn't work
>> at all. If I have both :
>>
>> scu.exe : svn:executable
>> SCU.EXE : svn:executable
>>
>> in the config file, it will only attach the property on
>> the first definition it comes across: in other words, for
>> the example above filenames in lowercase are set but upper
>> case are not; and if you switch the order (put the upper
>> case first in the file) then it attaches the property only
>> on the upper case file.
>>
>> Obviously, from the documentation, the * regular expression
>> wild-card works. What other regular expressions work? Why
>> doesn't 2 different names work?
>>
>> Using svn: 1.2.1 on Linux,
>> 1.3 on Windows
>> and am seeing the same behavior on both.
>
> Due to the way the Subversion config file parser works you can't have
> two autoprops that differ only in case. I agree this is kind of
> insane, but we can't change it for backwards compatibility reasons.
> There's an issue about it someplace...
Here's the issue, which is currently being considered for Subversion
1.6 (though it's been delayed before and could be delayed again):
http://subversion.tigris.org/issues/show_bug.cgi?id=2036
Here are some prior mailing list threads on the topic:
http://svn.haxx.se/users/archive-2005-06/1170.shtml
http://svn.haxx.se/dev/archive-2005-08/1049.shtml <-- this apparently
includes a workaround you can use now
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Problem with auto-props patterns
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 6/13/06, Kelley T-Freytag <kf...@fnal.gov> wrote:
> I am trying to automatically set a svn property on a file
> called scu.exe. I want the property set regardless of
> the case of the file name, e.g both scu.exe and SCU.EXE.
> Putting scu.exe in the config file catches the lower case only.
> Putting something like [Ss][Cc][Uu].[Ee][Xx][Ee] doesn't work
> at all. If I have both :
>
> scu.exe : svn:executable
> SCU.EXE : svn:executable
>
> in the config file, it will only attach the property on
> the first definition it comes across: in other words, for
> the example above filenames in lowercase are set but upper
> case are not; and if you switch the order (put the upper
> case first in the file) then it attaches the property only
> on the upper case file.
>
> Obviously, from the documentation, the * regular expression
> wild-card works. What other regular expressions work? Why
> doesn't 2 different names work?
>
> Using svn: 1.2.1 on Linux,
> 1.3 on Windows
> and am seeing the same behavior on both.
Due to the way the Subversion config file parser works you can't have
two autoprops that differ only in case. I agree this is kind of
insane, but we can't change it for backwards compatibility reasons.
There's an issue about it someplace...
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org