On 27 June 2011 06:29, John Emmas <johne53_at_tiscali.co.uk> wrote:
> About a month ago I posted a question about line-ending styles. Just to recap, I'm running TSVN under Windows although I'm using it with a cross-platform project that uses *nix style line endings. I soon realised that when applying patches etc, I would often end up with Windows style line endings. A couple of people helped me to find (and set) my preferred eol style. And it works quite well - most of the time....
> Since then however, I've discovered that certain files stubbornly refuse to obey my preferred lstyle. I'm not talking about binary files - just plain vanilla C++ header files and source files. A high proportion of them (around 20 percent) seem to be stuck in my Windows native style (CRLF) even though they're theoretically set to my preferred style of LF (at least, that's what it says when I examine their properties).
> So let's say I select one or more of these files, open its TSVN Properties dialog and deliberately re-edit the eol style to CRLF. I apply the new style then I set it back again to LF. In both cases, TSVN goes through the motions and appears to be doing something. But at the end of the exercise, the files are still CRLF. Does anyone have any ideas about what could be wrong? Is it possible that TSVN thinks they're binary files for some reason?
I'm not sure that the line ending is changed on existing files in your
WC. If that property is already set in the repository copy, what
happens if you delete the local copy of the file and then update to
force a fresh copy to be created?
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-06-27 10:13:58 CEST