DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=MHBuHl9OJvzc4/t20ExVbCprL82xBv0Q9W/MomFB8lR
	+opuWai/cfgLJ5+5wfZ2mLz1f3Gg+BRr8U1jsfJlDSfYRANU1Obc6uIiUebQjAtP
	7g/TDDowVacVBqljTuD/13MKfumd4WTjNkvhjB2wlBLBdPK0TCJfB2HChlLqpChU
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <525499E5.4090608@etr-usa.com>
Date: Tue, 08 Oct 2013 17:48:53 -0600
From: Warren Young <warren@etr-usa.com>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: checking in >= 256k file fatally corrupts rcs file
References: <20131008102204.GB9241@plunk.org>
In-Reply-To: <20131008102204.GB9241@plunk.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

On 10/8/2013 04:22, Don Hatch wrote:
>
> Checking in a text file of size >= 256k
> corrupts the rcs file, irretrievably losing most of the contents

It's documented in the rcs NEWS file:

     - Env var RCS_MEM_LIMIT controls stdio threshold.

       For speed, RCS uses memory-based routines for files up to
       256 kilobytes, and stream-based (stdio) routines otherwise.
       You can change this threshold value by setting the environment
       variable ‘RCS_MEM_LIMIT’ to a non-negative integer, measured in
       kilobytes.  An empty ‘RCS_MEM_LIMIT’ value is silently ignored.

So, use the new environment variable, or build up your huge diffs a few 
steps at a time, so as to avoid spamming this buffer.

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