From: Warren Young <warren@etr-usa.com>
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: checking in >= 256k file fatally corrupts rcs file
Date: Wed, 09 Oct 2013 01:30:00 -0000 [thread overview]
Message-ID: <5254B1C0.9020004@etr-usa.com> (raw)
In-Reply-To: <20131009003055.GA30082@plunk.org>
On 10/8/2013 18:30, Don Hatch wrote:
> On Tue, Oct 08, 2013 at 05:48:53PM -0600, Warren Young wrote:
>> 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:
>
> That quote certainly doesn't describe or justify the very serious
> corruption bug I'm seeing in any way;
I'm not trying to justify it. I'm just pointing out that you have an
expedient workaround for the bug which lets you run on current versions
of Cygwin rcs.
> it would be really good if the feature
> could be backed out, and possibly re-introduced at a later time
> after it has been re-worked so that doesn't break the product.
If the bug affects GNU rcs on all platforms, it needs to be fixed
upstream. Then Cygwin rcs will get the fix when the Cygwin rcs package
maintainer updates the packages.
If the bug is in the Cygwin rcs port or in Cygwin itself, the actual bug
needs to be fixed, rather than hack out the feature that tickles the bug.
--
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
next prev parent reply other threads:[~2013-10-09 1:30 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
2013-10-09 0:24 ` Don Hatch
2013-10-09 1:30 ` Warren Young [this message]
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=5254B1C0.9020004@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).