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

Re: svn:eol-style native problem -- URGENT !!!

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Tue, 4 Nov 2008 00:16:34 +0000

2008/11/3 narengokal <naren.gokal_at_bcx.co.za>:
> I am setting all folders to have the "native" setting to elimnate the
> control chars when checking out into unix. The setting is done on my windows
> machine when i import my files.
> BUT, when i do a checkout in my unix box, most of the files are correctly
> converted, ie no control M chars, but 2 or 3 of these files do have these
> funny chars. Now, i can't see why this is happening. Please can someone
> assist , Urgently

The best way to be ignored on a public mailing list is to demand an
urgent response. Do you really think people are going to drop what
they are doing just because you put that in the title.

You cannot set svn:eol-style on a folder. When you add that property
recursively to a folder it gets applied to all the files which exist
in the folder at that time, but it is not set on the folder. In
consequence, if you subsequently add more files, you have to set the
svn:eol-style on them too - it does not happen automatically.

You can use subversion's auto-props feature, or TortoiseSVN's
tsvn:autoprops feature to ensure this property is added to files with
particular extensions. Look in the manual for more details.


:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
To unsubscribe, e-mail: dev-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: dev-help_at_tortoisesvn.tigris.org
Received on 2008-11-04 01:16:46 CET

This is an archived mail posted to the TortoiseSVN Dev mailing list.