X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 tests=BAYES_00,DKIM_ADSP_NXDOMAIN,SPF_HELO_PASS,TW_SV,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Gary Subject: Re: svn Date: Thu, 10 Feb 2011 21:03:01 +0100 Lines: 23 Message-ID: <83vd0rmzd6.fsf@garydjones.name> References: <4D540927 DOT 9030000 AT cs DOT umass DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (cygwin) X-No-Archive: Yes X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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? > (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. > (c) what line terminator, etc., VC# wants to see. Hmm. Well, I would hope that "svn co ." 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? 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. -- 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