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:from:to:subject:date; q=dns; s=
	default; b=EEzeNXPK4mfWWnZSQ3h7QbkXTo1MXTUWQ9yztcpweBhSvzsFbIZyg
	fFMdVmWNomkl0e2dkzsZ4tj1DTBuPbvAG+dgOLQMeg0ausLhViwa19550JhtjjNA
	TaUPW/p1DESZAl7Q6wR9er5+zFwyq4DycDZeDmaDrTEdIxqjVlizME=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <694832.7961.bm@smtp113.sbc.mail.ne1.yahoo.com>
From: tednolan AT bellsouth DOT net
To: cygwin AT cygwin DOT com
Subject: Wow, just hit RCS bug
Date: Wed, 16 Apr 2014 12:09:22 -0400

I just hit the worst Cygwin bug I've encountered, the RCS bug which
silently corrupts text files > 256K.  That's the last thing I expect
from a version control system!

After some moments of panic, I was able to retrieve a good copy from
backups, but have lost my revision history.

Anyway, I immediately did a list search and found this is a known bug.

Shouldn't this package be pulled?

Just for the record, the suggested env var fix

RCS_MEM_LIMIT=0

to "force stdio" does not work for me, but the

RCS_MEM_LIMIT=10240

to allow 10megs of diffs does..

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