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

Re: svn add: Unrecognized line ending style

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Wed, 7 Jul 2010 09:34:35 +0200

On Wed, Jul 7, 2010 at 7:57 AM, Aaron Turner <synfinatic_at_gmail.com> wrote:
> On Tue, Jul 6, 2010 at 10:34 PM, Henrik Sundberg <storangen_at_gmail.com> wrote:
>> On Wed, Jul 7, 2010 at 7:06 AM, Aaron Turner <synfinatic_at_gmail.com> wrote:
>>>> echo "hi" >foo.c
>>>> svn add foo.c
>>> svn: Unrecognized line ending style for 'foo.c'
>>>
>>>> echo -n "hi" >foo.c
>>>> svn add foo.c
>>> svn: Unrecognized line ending style for 'foo.c'
>>>
>>>> echo "hi" >foo
>>>> svn add foo
>>> A         foo
>>>
>>> Ideas anyone?
>>
>> What does your autoprops configuration for c files look like?
>> Is the value for line ending style misspelled?
>> (no erroneous value is set for the non-c file)
>>
>> /$
>
>
> *.c = svn:eol-style=native, svn:keywords=Id HeadURL Author Rev Date
>
> Honestly, I'm 99.9% sure that this problem started after upgrading to
> 1.6.12... nothing else changed that I can think of.

I quickly checked the relevant section in the svn book:

http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html#svn.advanced.confarea.opts.config

which says that multiple properties must by semi-colon-delimited ("It
contains any number of key-value pairs in the format PATTERN =
PROPNAME=VALUE[;PROPNAME=VALUE ...]"). In your config file it's
comma-delimited, so maybe that's the problem. Maybe the parser of the
autoprops was more tolerant before 1.6.12?

Cheers,

-- 
Johan
Received on 2010-07-07 09:36:13 CEST

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.