Re: File encoding for files ported between Mac and Windows?
Re: File encoding for files ported between Mac and Windows?
- Subject: Re: File encoding for files ported between Mac and Windows?
- From: Clark Cox <email@hidden>
- Date: Tue, 5 Jan 2010 20:45:23 -0800
On Tue, Jan 5, 2010 at 11:12 AM, Alastair Houghton
<email@hidden> wrote:
> On 5 Jan 2010, at 18:54, Dix Lorenz wrote:
>
>> How are you porting the files? You should be using some kind of Version Control System anyway and that way, when you check the sources out, they will be correctly formatted for the platform you are on.
>
> That's actually a *massive* mis-feature of many version control systems. Why?
> Because many people have network-based home directories (particularly in larger
> companies) and this kind of abject stupidity from SCM systems commonly results in
> huge change sets full of line ending changes simply because someone checked code out
> on one platform (to their home folder, which is mounted in more than one place) and then
> checked in on another.
Then just turn that feature off :) I don't think I've seen an SCM
system where line ending conversions are *mandatory*. If the feature
doesn't work in your situation, don't use it:) I'd argue that the
common case is one where a checked-out working copy never leaves the
machine (much less platform) where it was initially checked out. In
that case, the line-ending translation is most certainly not a
mis-feature.
--
Clark S. Cox III
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden