This is the mail archive of the
mailing list for the Cygwin project.
Re: checking in >= 256k file fatally corrupts rcs file
- From: Warren Young <warren at etr-usa dot com>
- To: Cygwin-L <cygwin at cygwin dot com>
- Date: Tue, 08 Oct 2013 17:48:53 -0600
- Subject: Re: checking in >= 256k file fatally corrupts rcs file
- Authentication-results: sourceware.org; auth=none
- References: <20131008102204 dot GB9241 at plunk dot org>
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:
- Env var RCS_MEM_LIMIT controls stdio threshold.
For speed, RCS uses memory-based routines for files up to
256 kilobytes, and stream-based (stdio) routines otherwise.
You can change this threshold value by setting the environment
variable ‘RCS_MEM_LIMIT’ to a non-negative integer, measured in
kilobytes. An empty ‘RCS_MEM_LIMIT’ value is silently ignored.
So, use the new environment variable, or build up your huge diffs a few
steps at a time, so as to avoid spamming this buffer.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple