public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Warren Young <warren@etr-usa.com>
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: checking in >= 256k file fatally corrupts rcs file
Date: Tue, 08 Oct 2013 23:49:00 -0000	[thread overview]
Message-ID: <525499E5.4090608@etr-usa.com> (raw)
In-Reply-To: <20131008102204.GB9241@plunk.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
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2013-10-08 23:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 10:16 Don Hatch
2013-10-08 23:49 ` Warren Young [this message]
2013-10-09  0:24   ` Don Hatch
2013-10-09  1:30     ` Warren Young
2013-10-09  2:07       ` Gary Johnson
2013-10-09  3:29         ` Warren Young
2013-10-09  6:59       ` Don Hatch
2013-10-09 13:37         ` Warren Young
2013-10-09 14:00           ` Ryan Johnson
2013-10-09 17:58           ` Don Hatch
2013-10-09 13:47   ` Ryan Johnson
2013-10-09 18:28     ` Achim Gratz
2013-10-09 20:57       ` Richard Gribble
2014-02-26 13:26 Wagemans, Peter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=525499E5.4090608@etr-usa.com \
    --to=warren@etr-usa.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).