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

Re: Changing the behaviour of eol-style "native"

From: David Huang <khym_at_azeotrope.org>
Date: Sat, 9 Jan 2010 15:12:58 -0600

On Jan 9, 2010, at 2:19 PM, Stu Redman wrote:

> Stu Redman wrote:
>
> (Sigh, that's why I don't like mailing lists. No idea why this is bundled with the other issue now.)
>
> I should point out I'm not sharing a working copy. I ignore the .svn
> dirs at replicate, so the result is not a wc any more.
> Responses like "any decent text editor or tool should" are not helpful,
> guys. I develop and test on Windows, then replicate to Linux to test
> there, and got no suggestion how to do this in a better way. The problem
> are not Linux editors, but other tools (msgmerge, automake, bash, awk)
> that behave in the "we are Linux and who cares about Windows" way. I
> can't change these tools. What is your intention? Are you trying to tell
> me I better stop using TSVN and go for a Linux SVN client?
> I take it there is no option to set the "native" mode at the moment, but
> I believe I have a valid use case and it would be a very little thing to
> change.

As Andy Levy has already suggested, if you need the files to have LF endings, eol-style should be LF, not native. It seems strange to want a new setting to treat "native" as "LF" when a setting to get LFs already exists.

Name: Dave Huang | Mammal, mammal / their names are called /
INet: khym_at_azeotrope.org | they raise a paw / the bat, the cat /
FurryMUCK: Dahan | dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 33 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2435983

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-01-09 22:13:38 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.