[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: Felix Saphir <felix.saphir_at_presswatch.de>
Date: Sat, 09 Jan 2010 23:40:39 +0100

Nathan Tuggy schrieb:
> On 2010-01-09 14:13, Felix Saphir wrote:
>> Stu Redman schrieb:
>>> 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.
>> You can - they're open source ;-)
> Yes, they are, but it occurs to me that this is not very helpful -- how
> much work would it be to fix msgmerge, automake, bash, and awk (and
> others) to handle CRLFs properly? Between 10 and 50 hours each, I should
> think, which is generally completely out of the question. Most of that
> time is simply getting set up to make changes to the code -- there's
> likely to be a 100-500% overhead dealing with small issues like this.
> I'm a great fan of open-source, but just being able to look at the
> source doesn't fix every inefficiency and flaw automatically.
> Fortunately, I suspect using eol-style=LF would do the job, or keeping
> separate WCs.

Exactly. The point is, that the requested change would almost certainly
break other peoples working copies if they don't (can't?) change their
tools accordingly.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-01-09 23:50:13 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.