Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <00a501c46d5c$3b258530$78d96f83@robinson.cam.ac.uk>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: "Karr, David" <david DOT karr AT wamu DOT net>, <cygwin AT cygwin DOT com>
References: <0C260F619E428642BFA6380177C3ADF30126AD76 AT exmsea005 DOT us DOT wamu DOT net>
Subject: Re: Subversion eol-corrupting jar files on update
Date: Mon, 19 Jul 2004 07:47:12 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Note-from-DJ: This may be spam

Karr, David wrote:
>> I'm having trouble with the svn in Cygwin corrupting jar
>> files on update or checkout.  It's doing an eol translation.
>> I've specified ".jar" in my svn properties, to indicate that
>> it should use the "eol-type" of "native".  My "mount" table
>> shows everything in "textmode".  Do I have to change to
>> binary in order for this to work?  I would have thought the
>> eol-type setting in the subversion config should deal with this.
> If the Cygwin port of subversion is really just using the mount mode to
> determine this, then that seems like a bug to me.  Someone else pointed
> out to me that subversion is able to determine that the "mime-type" of
> ".jar" is "application/octet-stream", and that should imply that it
> should do no file conversion.

Ugh, textmode. Been so long since I've used it, I'd forgotten about it.

/me mentally prepares himself for adding a slew of binary flags.

Max.


--
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/