Re: annoyance: servers file format-- worked before 1.6.11

On Thu, Apr 26, 2012 at 12:31:29PM -0600, Will Fleming wrote:
> [etldev_at_odlbods1 ~]$ svn help
> svn: /home/etldev/.subversion/servers:153: Option expected
> [etldev_at_odlbods1 ~]$
>
> I removed the leading spaces to the line setting and then it worked
> ......
> # No neon-debug-mask, so neon debugging is disabled.
> # ssl-authority-files = /path/to/CAcert.pem;/path/to/CAcert2.pem
> #
> # Password / passphrase caching parameters:
> # store-passwords = no
> store-plaintext-passwords = no
> # store-ssl-client-cert-pp = no
> # store-ssl-client-cert-pp-plaintext = no
> ....
>
> Prior to 1.6.11, there could be leading spaces on that line

Are you sure about that? I don't have a 1.6.10 release build around
but I see the same behaviour with a Subversion 1.5 build.

Note that the parser does this because a leading space is usually
used in multi-line configuration statements.
For instance, given an entry such as:

global-ignores = *.o *.lo *.la *.al .libs *.so *.so.[0-9]* *.a *.pyc *.pyo
   *.rej *~ #*# .#* .*.swp .DS_Store

both lines will be merged into one by the config parser. The second line
is part of the previous one because it starts with whitespace.

I don't think this is very intuitive myself. Alas, that's how it was designed.
Received on 2012-04-26 20:50:37 CEST