• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: File encoding for files ported between Mac and Windows?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: File encoding for files ported between Mac and Windows?


  • Subject: Re: File encoding for files ported between Mac and Windows?
  • From: Paul M <email@hidden>
  • Date: Wed, 6 Jan 2010 21:20:03 +1300

<a bit OT>
As I'm reading this, I'm working with source files that reside on a unix
fileserver in the next room. I'm editing on my Mac, but compiling and
debugging in codewarrior on a windows laptop via samba. (Unfortunately,
I'm targetting an embedded device that's unsupported by XCode.)
Sounds painful, but it's not, it works really well - it's far less painfull
than using the awfull windows editor.


For source control I'm using CVS from the command line on the unix box. All
my files have unix line endings and have never been a problem.


Sorry for the distraction, I'll let you get back to work now ...


paulm


On 6/01/2010, at 5:45 PM, Clark Cox wrote:

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


_______________________________________________ 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
References: 
 >File encoding for files ported between Mac and Windows? (From: Howard Moon <email@hidden>)
 >Re: File encoding for files ported between Mac and Windows? (From: Dix Lorenz <email@hidden>)
 >Re: File encoding for files ported between Mac and Windows? (From: Alastair Houghton <email@hidden>)
 >Re: File encoding for files ported between Mac and Windows? (From: Clark Cox <email@hidden>)

  • Prev by Date: Re: SLA agreements for Disk Image
  • Next by Date: Re: File encoding for files ported between Mac and Windows?
  • Previous by thread: Re: File encoding for files ported between Mac and Windows?
  • Next by thread: Re: File encoding for files ported between Mac and Windows?
  • Index(es):
    • Date
    • Thread