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/cygwi
Dear Dr. Zell,
> [ANNOUNCEMENT] Updated: rcs-5.8.1-1: The Revision Control System
Do you perhaps know whether this version fixes the file corruption
problem noticed earlier on this list for 5.8, or should we stay with
5.7 to avoid corrupting large RCS files?
Short problem description (what I th
Brian Wilson wrote:
> From what I've read in this discussion, I think the issue is that
> the '^M' characters may not be seen by RCS as an EOL.
The problem occurs in a loop that copies one character at a time to
move the entire content of the work file into the new RCS file as the
latest version
Richard Gribble wrote:
> I have experienced this problem several times. In my case it seemed
> to be a problem between 'Unix' and 'DOS' files. In each case, I
> have been able to fix it by editing the RCS file using vim and
> deleting all the extraneous carriage returns
RCS should be able to h
4 matches
Mail list logo
