From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2200 invoked by alias); 9 Oct 2013 01:30:40 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 2184 invoked by uid 89); 9 Oct 2013 01:30:39 -0000 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 Received: from etr-usa.com (HELO etr-usa.com) (130.94.180.135) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 09 Oct 2013 01:30:39 +0000 Received: (qmail 40429 invoked by uid 13447); 9 Oct 2013 01:30:37 -0000 Received: from unknown (HELO [172.20.0.42]) ([107.4.26.51]) (envelope-sender ) by 130.94.180.135 (qmail-ldap-1.03) with SMTP for ; 9 Oct 2013 01:30:37 -0000 Message-ID: <5254B1C0.9020004@etr-usa.com> Date: Wed, 09 Oct 2013 01:30:00 -0000 From: Warren Young 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 Subject: Re: checking in >= 256k file fatally corrupts rcs file References: <20131008102204.GB9241@plunk.org> <525499E5.4090608@etr-usa.com> <20131009003055.GA30082@plunk.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 X-SW-Source: 2013-10/txt/msg00100.txt.bz2 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