Re: Repository-defined autoprops.

On 5/27/05, Chris Foote <cfoote@v21.me.uk> wrote:
> ----- Original Message -----
> From: <kfogel@collab.net>
> To: "SteveKing" <steveking@gmx.ch>
> Sent: Friday, May 27, 2005 9:29 PM
>
>
> > > Disadvantage:
> > > - only per-repository, not per-folder (even though the config file
> > > could have sections for subfolders)
> >
> > No need to have sections, it can just use paths.
> >
> Using sections would make the file easier to read/use IMO.
>
> Suppose you want to apply eol=native in all directories except those
> under the /projA/trunk directory.
>
> e.g. no sections
> [auto-props]
> *.c = svn:eol-style=native
> *.h = svn:eol-style=native
> /projA/trunk/*.c = svn:eol-style=CRLF
> /projA/trunk/*.h = svn:eol-style=CRLF

This also has the (previously noted by implication) problem that order
of application is not guaranteed now; this would have to change to
permit "overriding" of props. I can see reasonable arguments for
either (reverse-)order-appearing-in-config-file or length-of-match
precedence.

-- 
Regards,
Charles Bailey
Lists: bailey _dot_ charles _at_ gmail _dot_ com
Other: bailey _at_ newman _dot_ upenn _dot_ edu
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org