From: Ian Miller <ian@gingerspice.demon.co.uk>
To: Cygwin Mailing List <cygwin@sourceware.cygnus.com>
Subject: RCS 5.7 & bin/text mounts
Date: Thu, 03 Feb 2000 16:31:00 -0000 [thread overview]
Message-ID: <389A1DF1.EF1A37FD@gingerspice.demon.co.uk> (raw)
Hi, I'd like some advice on how I can make best use of the RCS 5.7 port
for Cygwin B20. The README file says:-
- the package has been built for binary mounts and not tested on
nonbinary ones. But as RCS internally handles its files in UN*X
LF format I don't expect it to work.
However, I have all my partitions mounted as text!=binary as recommended by
various posters and FAQs. I used to use the DJGPP port of RCS in conjunction
with NTEmacs 20.x and had no problems; but now if I check stuff in and out
using NTEmacs and my old RCS files, I get corrupted RCS files, though it
seems to work perfectly with newly created RCS files!
[I believe NTEmacs adopts the "approved" Cygwin approach of removing the
CR's for display and replacing them when the file is written (even though
it is not itself a Cygwin port)? ]
I don't understand why there should be a problem with using this port of
RCS with text mounts, because surely it just means that extra characters
are checked in and out (i.e. the CR's)? I presume the DJGPP port did something
different re: the CR/LF situation, and that is why I am having trouble
checking in/out old files? Please advise!
cheers,
ian
--
+------------------------------+----------------------------------------------+
| ian miller | My other MUA is a GNU. |
| ian@gingerspice.demon.co.uk | http://www.gingerspice.demon.co.uk |
+------------------------------+----------------------------------------------+
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-02-03 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-03 16:31 Ian Miller [this message]
2000-02-03 16:44 ` Ian Miller
2000-02-04 9:03 ` Andre Oliveira da Costa
2000-02-04 9:56 Rick Rankin
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=389A1DF1.EF1A37FD@gingerspice.demon.co.uk \
--to=ian@gingerspice.demon.co.uk \
--cc=cygwin@sourceware.cygnus.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).