Re: MacOSX-dev digest, Vol 1 #904 - 22 msgs
Re: MacOSX-dev digest, Vol 1 #904 - 22 msgs
- Subject: Re: MacOSX-dev digest, Vol 1 #904 - 22 msgs
- From: Bill Bumgarner <email@hidden>
- Date: Wed, 27 Jun 2001 11:36:18 -0400
Stephane nailed it with that explanation.
One additional bit of information that may save someone a bit of
sanity; Windows implementation of RSH happily translates EOL characters
"on the pipe". Even if you mark a gif image as "handle as a binary",
using rsh as a transport mechanism with CVS will very likely lead to
corrupt images on update or commit.
I believe pserver avoids this problem, but keep in mind that pserver is
inherently insecure (passwords go across the wire pretty much as
plaintext).
Ssh is the way to go; you can find an ssh command line binary for
windows on the net. It isn't easy, but they exist (I can't remember
where we picked ours up, at this point). Ssh has the advantage of
security and compression (yes, CVS has compression, to, but ssh has
general purpose connectivity compressin-- try port forwarding a database
connection with compression turned on and you'll see a 70% or so
performance improvement!).
b.bum
On Wednesday, June 27, 2001, at 06:20 AM, macosx-dev-
email@hidden wrote:
Excellent explanation of line endings and conversion nastiness mostly
deleted... relevant included below.
This is of highest importance when you are working under Windows!
Note that in this case, be careful with files which are (or could
be) saved using Unicode encoding (like *.wod, *.html, *.strings):
they MUST be treated as binary files, else cvs will corrupt Unicode
by replacing sequence LF with CRLF on Windows. You'd better check
that your editors (ProjectBuilder, WebObjectsBuilder) don't use
Unicode encoding (nor UTF-8?), but Windows Latin 1 for example, which
is an 8-bit character encoding.