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

Re: Doubt about auto properties

From: Martin Furter <mf_at_rola.ch>
Date: 2003-10-09 20:26:30 CEST

On 9 Oct 2003, Lele Gaifax wrote:

> Hi all,
> I'm using the new auto-props feature (very welcome ;-) The doc in
> config_file.c states:
> ### Section for configuring automatic properties.
> ### The format of the entries is:
> ### file-name-pattern = propname[=value][;propname[=value]...]
> ### The file-name-pattern can contain wildcards (such as '*' and
> ### '?'). All entries which match will be applied to the file.
> ### Note that auto-props functionality must be enabled, which
> ### is typically done by setting the 'enable-auto-props' option.
> My doubt is on that "All entries which...": it seems that it is /not/
> cumulative, as I assumed reading that comment; infact, if I put
> something like
> *.rst = svn:eol-style=native
> *.rst = svn:keywords=LastChangedDate LastChangedRevision LastChangedDate LastChangedBy HeadURL
> in my [auto-props] section, doing an "svn add file.rst" results in a
> addition that carries only the latter one, I mean, the eol-style
> keyword is not set.
> The job works if I join the two lines, as in
> *.rst = svn:eol-style=native;svn:keywords=LastChangedDate LastChangedRevision LastChangedDate LastChangedBy HeadURL
> Am I missing the point, or is that comment misleading?

The config is stored in apr hashes so i assume that the value of the
former one was replaced by that of the latter one when reading the config.

To make the config more readable you could write it this way:

*.rst = svn:eol-style=native;
        svn:keywords=LastChangedDate LastChangedRevision LastChangedDate LastChangedBy HeadURL


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 9 20:28:47 2003

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.