public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Keith Christian <keith1christian@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Wow, just hit RCS bug
Date: Wed, 16 Apr 2014 22:20:00 -0000	[thread overview]
Message-ID: <CAFWoy7HdXgKXnPKNTsEUo38ttbj=fCR4kRRoLnSyxdvFuoffTA@mail.gmail.com> (raw)
In-Reply-To: <112218.65526.bm@smtp118.sbc.mail.ne1.yahoo.com>

RCS does a great job for smaller projects when I don't need the
overhead of any of the popular larger systems.  It has saved me many
times when I'm working on a short document or a set of scripts on my
desktop machine.

I'd miss it if it were removed simply due to the lack of handling
10Meg of diffs or similar.  Wonder if this bug could be fixed some
way?

On Wed, Apr 16, 2014 at 11:05 AM,  <tednolan@bellsouth.net> wrote:
> In message <87bnw12nuu.fsf@Rainer.invalid>you write:
>>tednolan@bellsouth.net writes:
>>> Just for the record, the suggested env var fix
>>>
>>> RCS_MEM_LIMIT=0
>>>
>>> to "force stdio" does not work for me, but the
>>
>>That was never suggested as a fix, but to show that the problem occurs
>>with files much less than 256kiB size when forcing the code path through
>>stdio (which is what the "0" setting does).  The RCS test suite passes
>>on Cygwin since it never actively tests this code path.
>>
>>http://thread.gmane.org/gmane.os.cygwin/142346
>>
>>> RCS_MEM_LIMIT=10240
>>>
>>> to allow 10megs of diffs does..
>>
>>Which will fail once you happen upon a diff that gets that large.
>>
>
> Ah, OK -- I was just looking for a fix or workaround and didn't read
> what the "=0" was supposed to do closely enough.
>
> I can't see ever getting up to 10M of diffs, but still I consider
> it an "existential" level bug for a version control system and think
> the package should be removed.  It's almost as bad as if "ls -l foo"
> unlinked "foo".
>
> --
> 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
>

--
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:[~2014-04-16 22:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-16 16:41 tednolan
2014-04-16 17:20 ` Achim Gratz
2014-04-16 17:38   ` tednolan
2014-04-16 22:20     ` Keith Christian [this message]
2014-04-16 22:25       ` tednolan
2014-04-17  1:04 ` Wow, just hit RCS bug (attn: Dr Volker Zell) Warren Young
2014-04-17  8:21   ` Achim Gratz
2014-04-17 14:01     ` Achim Gratz
2014-04-18  9:14   ` peter.wagemans
2014-04-18 12:07     ` peter.wagemans

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='CAFWoy7HdXgKXnPKNTsEUo38ttbj=fCR4kRRoLnSyxdvFuoffTA@mail.gmail.com' \
    --to=keith1christian@gmail.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).