[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: Aaron Turner <synfinatic_at_gmail.com>
Date: Thu, 8 Jul 2010 09:14:10 -0700

On Thu, Jul 8, 2010 at 1:22 AM, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> Aaron Turner wrote on Wed, 7 Jul 2010 at 18:12 -0000:
>> On Wed, Jul 7, 2010 at 12:34 AM, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
>> > On Wed, Jul 7, 2010 at 7:57 AM, Aaron Turner <synfinatic_at_gmail.com> wrote:
>> >> *.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?
>>
>>
>> Bingo. That was it.  Thanks for solving that mystery!
>>
>
> For the record, I can't reproduce it with trunk:
>
> % svn add iota3 --config-option=config:auto-props:*.c="svn:eol-style=native, svn:keywords=Id"
> A         iota3
> %

You need to add a .c file :) It only breaks if the filename matches the rule.

-- 
Aaron Turner
http://synfin.net/         Twitter: @synfinatic
http://tcpreplay.synfin.net/ - Pcap editing and replay tools for Unix & Windows
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
    -- Benjamin Franklin
"carpe diem quam minimum credula postero"
Received on 2010-07-08 18:16:11 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.