DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=D8Yw
	E4r4Tz31aS7m0aFAfqY+/ZY5rze61e+wyuOfof3//3KRsMMOMMN4+jGk6UbC4zWZ
	sZfcm965kC9wUi8WcjJzfEV3fa+mjGYAzQOWmN5S3Yfv9IKrfiMvM79GbAGeWASg
	wtCpEK4+P9AJWMlqk5VQMIrg1/a2LMSIFFKkTk8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Tue, 8 Oct 2013 19:08:13 -0700
From: Gary Johnson <garyjohn@spocom.com>
To: cygwin@cygwin.com
Subject: Re: checking in >= 256k file fatally corrupts rcs file
Message-ID: <20131009020813.GA15389@phoenix>
Mail-Followup-To: cygwin@cygwin.com
References: <20131008102204.GB9241@plunk.org> <525499E5.4090608@etr-usa.com> <20131009003055.GA30082@plunk.org> <5254B1C0.9020004@etr-usa.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5254B1C0.9020004@etr-usa.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On 2013-10-08, Warren Young wrote:
> 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.

There was a discussion around March 27, 2012, about another change
in the behavior of RCS between 5.7 and 5.8.  It appears that someone
decided to make some sweeping "improvements" to RCS and broke a few
things along the way.

Regards,
Gary


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