X-Recipient: archive-cygwin AT delorie DOT com
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=ecu4lEJOmpjv6wGA1/ArArQnGHoreY3kfS4Js6iDdwS
	+B379e6z6jp82b8o2L9ijZvwQM8XjYS7VMwXmdO4Pw+a0c70gewFa4oSs2gop9tD
	5MAymrkajnsnAvH+7ncQlC+6Q0nRNnzlscD65Q3Y11Xe3ARj71+k4M/AJv+vdNp4
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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;
	 s=default; bh=ZOxq83UmgniyooXoqf8DQrIOaqs=; b=q8uw3IZE2RTmp9fgY
	MHTVimAIaT1ArlPnQmrkjMiNHeVdBh0NhVicwqciOAlJ4V2UWXZpmlzzjPHPmF4C
	qnFPbh3LwOnKavLMhLhyoRU2XPBwsw7zrQfIRqdX6MllIB6o3B5qfAyY234xRnmJ
	tAhscz1hlLtg9BP/QQEe1NF9QA=
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
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO: etr-usa.com
Message-ID: <5254B1C0.9020004@etr-usa.com>
Date: Tue, 08 Oct 2013 19:30:40 -0600
From: Warren Young <warren AT etr-usa DOT 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 AT cygwin DOT com>
Subject: Re: checking in >= 256k file fatally corrupts rcs file
References: <20131008102204 DOT GB9241 AT plunk DOT org> <525499E5 DOT 4090608 AT etr-usa DOT com> <20131009003055 DOT GA30082 AT plunk DOT org>
In-Reply-To: <20131009003055.GA30082@plunk.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 10/8/2013 18:30, Don Hatch wrote:
> On Tue, Oct 08, 2013 at 05:48:53PM -0600, Warren Young wrote:
>> 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:
>
> That quote certainly doesn't describe or justify the very serious
> corruption bug I'm seeing in any way;

I'm not trying to justify it.  I'm just pointing out that you have an 
expedient workaround for the bug which lets you run on current versions 
of Cygwin rcs.

> it would be really good if the feature
> could be backed out, and possibly re-introduced at a later time
> after it has been re-worked so that doesn't break the product.

If the bug affects GNU rcs on all platforms, it needs to be fixed 
upstream.  Then Cygwin rcs will get the fix when the Cygwin rcs package 
maintainer updates the packages.

If the bug is in the Cygwin rcs port or in Cygwin itself, the actual bug 
needs to be fixed, rather than hack out the feature that tickles the bug.

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