On Wed, Jul 7, 2010 at 12:34 AM, Johan Corveleyn <jcor...@gmail.com> wrote: > On Wed, Jul 7, 2010 at 7:57 AM, Aaron Turner <synfina...@gmail.com> wrote: >> On Tue, Jul 6, 2010 at 10:34 PM, Henrik Sundberg <storan...@gmail.com> wrote: >>> On Wed, Jul 7, 2010 at 7:06 AM, Aaron Turner <synfina...@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?
Bingo. That was it. Thanks for solving that mystery! -- 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"
