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

Re: Repository-defined autoprops.

From: Chris Foote <cfoote_at_v21.me.uk>
Date: 2005-05-28 01:20:09 CEST

----- 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
*.c = svn:eol-style=native
*.h = svn:eol-style=native
/projA/trunk/*.c = svn:eol-style=CRLF
/projA/trunk/*.h = svn:eol-style=CRLF

e.g. using sections.
*.c = svn:eol-style=native
*.h = svn:eol-style=native

*.c = svn:eol-style=CRLF
*.h = svn:eol-style=CRLF

Without using sections the [auto-props] list would soon get very long
and with a lot of repetition of paths.

> Better to have it in a subdirectory of the root. Greg Stein has a
> great solution for this:
> You put it in a subfolder named "/config". But, that's configurable,
> via an svn:config-dir property set on the root directory of the
> repository! So if people need to use "/config" for something else,
> they can just set that property. Subversion would always look where
> the property points; if no property, then default is "/config".
Is there any reason that this config couldn't be just a file in the repos
conf directory (where svnserve.conf is stored)?
As there is no need for the repository config to be versioned, is there?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 28 01:21:05 2005

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

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