X-Spam-Check-By:	sourceware.org
Message-ID:	<860934040609271632u5221c256v8b4db4c16bf669e3@mail.gmail.com>
Date:	Wed, 27 Sep 2006 16:32:36 -0700
From:	"Malcolm Nixon" <malcolm DOT nixon AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	RE: Bash 3.1.17(8) CR/LF problem
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Jonathan Arnold wrote:
> You can change the Perforce filetype to be binary, and that way Perforce
> will leave the cr/lf alone. Then check out the scripts, do a d2u on them,
> and check them back in.
>
>
> $ p4 edit -t binary myscript.sh

I believe this is what I will end up being forced to do. Many of the other
fixes could be used if this were just my system, however I have to
assist over 30 developers scattered around the country, most of whom
are Cygwin illiterate (other than running a simple build script).

The mount point idea would work, except that every developer gets their
local sandbox in different areas of their drives, and most have multiple
sandboxes active for work on different branches.

The only truly annoying thing with binary files in Perforce is that it
makes diffing and merging much harder.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -