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: "Paul Sanders" <email@hidden>
- Date: Thu, 7 Jan 2010 09:58:33 -0000
To add to my own post: what CVS is missing is the ability to
stipulate that certain files should have certain line-endings
applied on checkout. That would be very handy for shell scripts
(which need to be LF-only). But as I said before, one can just
run a little script after checking out a directory tree to put
that right.
CVS gets a lot of stick these days, but it's still alive and
kicking.
Paul Sanders.
----- Original Message -----
From: "Paul Sanders" <email@hidden>
To: "Clark Cox" <email@hidden>; "Alastair Houghton"
<email@hidden>
Cc: "Xcode Users" <email@hidden>
Sent: Thursday, January 07, 2010 9:49 AM
Subject: Re: File encoding for files ported between Mac and
Windows?
Not at all. It seems to me that you _want_ your line endings
normalised in the repository, and you want diffs and merges to
be line-ending-agnostic (which they are). Anything else would
cause mayhem.
Paul Sanders.
----- Original Message -----
From: "Clark Cox" <email@hidden>
To: "Alastair Houghton" <email@hidden>
Cc: "Xcode Users" <email@hidden>
Sent: Wednesday, January 06, 2010 11:08 PM
Subject: Re: File encoding for files ported between Mac and
Windows?
Then I guess I can count myself as lucky for never having used
CVS in any real capacity for a cross-platform product :)
--
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