X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_05,KHOP_THREADED,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org From: "Brian Wilson" To: cygwin AT cygwin DOT com Subject: Re: RCS file corruption. Date: Thu, 21 Jun 2012 17:09:48 -0400 Message-Id: <20120621210043.M43274@ds.net> In-Reply-To: <1256297426.20120622004455@mtu-net.ru> References: <1256297426 DOT 20120622004455 AT mtu-net DOT ru> X-OriginatingIP: 65.12.174.114 (wilson) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 > I suspect this happens because sometimes I edit the files on my Linux box and sometimes on my Windows box. If I remember correctly, RCS (and the earlier SCCS systems) were designed to work with source code (i.e. text files). They determined file changes based on lines added or deletes and had a fixed length internal buffer used to read each line. From what I've read in this discussion, I think the issue is that the '^M' characters may not be seen by RCS as an EOL. If that is the case, RCS will read the whole file as a single line and large files (>65KB) may not be properly handled. Use dos2unix and unix2dos to convert the files and you will probably eliminate the issue. My $0.02 Brian S. Wilson -- 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