X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.8 required=5.0	tests=AWL,BAYES_00,TW_SV,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Message-ID: <4D549BC6.8040403@cs.umass.edu>
Date: Thu, 10 Feb 2011 21:15:34 -0500
From: Eliot Moss <moss AT cs DOT umass DOT edu>
Reply-To: moss AT cs DOT umass DOT edu
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: svn
References: <ij1160$346$1 AT dough DOT gmane DOT org> <4D540927 DOT 9030000 AT cs DOT umass DOT edu> <83vd0rmzd6 DOT fsf AT garydjones DOT name>
In-Reply-To: <83vd0rmzd6.fsf@garydjones.name>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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

On 2/10/2011 3:03 PM, Gary wrote:
> Eliot Moss wrote:
>
>> I wonder if it has to do with
>> (a) what svn believes to be a text, as opposed to binary, file;
>
> Possibly. But... I shouldn't have to configure that for my svn client,
> should I? Isn't that supposed to be done on the repo end?

Yes and no.  The /subversion/config file is per-client and controls
a number of things, notably what sorts of files are treated as
binary and the eol (end of line) properties of text files.

>> (b) how you have cygwin set to treat text files; and
>
> Not sure what you mean here. You mean the mount options? Not sure what
> they are, I'm on a different computer right now.

Yes, I think so, but there is a place where, when you set up cygwin,
you indicate a preference for Windows or Linux line endings. That is
what I am talking about.  And if you set it for Linux (say) and Windows
tools don't like that (or vice versa) then you can have problems.

>> (c) what line terminator, etc., VC# wants to see.
>
> Hmm. Well, I would hope that "svn co<URL>  ." just gets whatever happens
> to be in the repo - LF, CRLF, whatever - and doesn't feck with them just
> because they are not the line endings some program someone might want to
> sometime use, expects. Is that not the case?

Ummm, no. The svn:eol-style property controls how line endings get
translated between the internal store and representation when checked
out.  This makes sense if you want the same sources to work on Mac OS,
Unix, and Windows, transparently ... the external and internal forms
cannot always match byte-for-byte.

> I should probably mention that I've been happily using the same Cygwin
> svn for about a year (including some binary files such as images) and
> never had a problem. Only now, with this stupid new project/repository.

Well, I hope you are starting to understand the eol representation issue
to which I am pointing.  I can't say if that's what's biting you, but
if someone set up a repo without doing that well, and you try building
on a platform that wants different line endings, your tools might well
complain or produce results different from what you want ...

Best wishes -- EM

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