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

Re: Problem with auto-props patterns

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2006-06-13 20:40:22 CEST

On 6/13/06, Kelley T-Freytag <kfreytag@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...


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 13 20:41:46 2006

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.