From: "Wagemans, Peter" <peter.wagemans@kpn.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: checking in >= 256k file fatally corrupts rcs file
Date: Wed, 26 Feb 2014 13:26:00 -0000 [thread overview]
Message-ID: <00CBC5201250E84D820DE79A91A2E7251664D0B940@EXCNLDCM02.europe.unity> (raw)
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
next reply other threads:[~2014-02-26 13:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 13:26 Wagemans, Peter [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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
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=00CBC5201250E84D820DE79A91A2E7251664D0B940@EXCNLDCM02.europe.unity \
--to=peter.wagemans@kpn.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).