>
> I'm using *.sh *.java *.sql *.ctl files ..
>
> >
> > Please do not top-post. Answers at the end.
You should check what this comment means and try and follow it. See:
http://learn.to/quote
More information on your set-up would be useful. I'm assuming that
since you are on the tortoise list that you are using TortoiseSVN as your
client for subversion. Is your working copy on Windows or unix? What
file sharing are you using? If its Samba the make sure you read the faq
section http://tortoisesvn.tigris.org/faq.html#samba
Setting the property eol-style=native will give you CRLF line endings
using a TortoiseSVN client (native means native to the client software,
not the destination filesystem). Setting the eol-style=LF property on the
files will fix this.
If you are using the command line client from the unix side then the files
you are having problems with either have the eol-style set, or they are
being interpreted as binary and not having any transformation done. In
which case they will be the same as when they were put in. Setting the
mime-type property should force these files the way you want then. See
the section "file content type" in the svn-book.
Alan
> >
> >>
> >>
> >> narengokal wrote:
> >>>
> >>> Hi,
> >>>
> >>> 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
> >
> > What specific file types do you have the problem on? Is the svn:mime-type
> > set?
> >
> > Simon
Received on 2008-11-05 20:26:30 CET