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:from:to:date:subject:message-id:content-type
	:content-transfer-encoding:mime-version; q=dns; s=default; b=K8I
	i+fzsVj9O2dchnSixfmS9oKL0CGw6jvncJ+21A0kbuqy7ZUfuG4LWFOLXaAIRuFt
	q4rMzdEUxQE8UTcm5AjnhH1aghXKIZAoQnc0z1PQDhc5Uku7exoNJDvX8nogw45V
	r3vKmbyKfg/3A8KIuLHJclQbbC4PAoA5tGepKVkM=
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:from:to:date:subject:message-id:content-type
	:content-transfer-encoding:mime-version; s=default; bh=NOB7dnYkN
	dDdSzQy0tzHiL4REwU=; b=IhmvLT73p87TSMn1Ha3aQB1XurmRu311N0rOpBBiD
	BkYcJt5MzCm92D50bJ03oLyd5+iLfcXba7V9VNtlubc2oClf7CdI2nwyokocPLwN
	ULPya4uoWlUTvfcqlC5y+Fu0O0dCwLkzPqG2hf5e1KL39gnJ+8koS0GhxSJqsurL
	5I=
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-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=1.4 required=5.0 tests=AWL,BAYES_50,KAM_ADVERT2,SPF_PASS autolearn=no version=3.3.2
X-HELO:	mail4.kpnnet.org
From:	"Wagemans, Peter" <peter DOT wagemans AT kpn DOT com>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Date:	Wed, 26 Feb 2014 14:01:08 +0100
Subject:	Re: checking in >= 256k file fatally corrupts rcs file
Message-ID:	<00CBC5201250E84D820DE79A91A2E7251664D0B940@EXCNLDCM02.europe.unity>
MIME-Version:	1.0
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id s1QD3XZK007417

This is an additional comment on the thread starting with

    http://cygwin.com/ml/cygwin/2013-10/msg00086.html

Recently I was bitten again by this RCS 5.8 bug after I
failed to keep RCS at version 5.7 during a Cygwin update.

The failure mechanism is described in

    http://cygwin.com/ml/cygwin/2012-09/msg00331.html

I never received a response from Dr. Volker Zell and didn't
know how to contact the RCS maintainers.

Since RCS 5.8 destroys large files I would prefer Cygwin to
keep RCS 5.7 available until 5.8 has been fixed. Or go to
5.9 if that doesn't have the same problem.

I've now tried to contact the RCS maintainers by submitting
a bug report:

    http://savannah.gnu.org/bugs/index.php?41707

Regards,

Peter Wagemans


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

- Raw text -