From: "Frank Schacherer" <Frank.Schacherer@memorec.com>
Cc: cvs-info@gnu.org
Subject: GNU Emacs, CVS, DOS and Unix
Date: Thu, 4 Dec 2003 18:53:49 +0100 [thread overview]
Message-ID: <64828F6F9921B040BD700B6C08D8CB8A27DA2B@megehermes.memorecbiotec.de> (raw)
Hi there,
I have a problem I have not been able to handle with browsing newsgroups
and reading the manuals.
My Problem: somewhere between Emacs, CVS and Samba, when I check my
files in
(1) there is a newline conversion, appending ^M
(2) the file privileges get changed, causing script files to lose their
executable status
I can remove the ^M's (and save) or not, when I refresh cvs-status,
PCL-CVS claims that the file is Up-To-Date.
I would like the file and it's rights to stay unchanged. I just can not
figure out where between Win-Emacs and it's CVS mode, Samba and CVS the
Problem lies, and how to stop it.
I am using the Windows port of GNU Emacs 21.2.1 (i386-msvc-nt5.0.2195),
together with PCL-CVS (which I do not know how to determine the Version
of).
I connect to a CVS 1.11.2 installation on a Redhat9 linux machine, which
I access via pserver. This CVS server has no fancy wrapper functions or
anything, it is more or less freshly installed out of the distribution.
The files I use are on a linux machine to which I have access via Samba,
and are Unix type files (I use C-x RET f unix to force Emacs to save
them as Unix files, and have Emacs set up to create Unix files for new
ones).
Any help would be appreciated!
Friendly Greetings
Frank
Dr. Frank Schacherer
<frank.schacherer(a)memorec.com> (Replace the (a) with @ for mailing.)
Memorec Biotec GmbH, a Miltenyi Biotec company
Stoeckheimer Weg 1, 50829 Koeln
phone +49 221 95048 308 fax +49 221 95048 144
next reply other threads:[~2003-12-04 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 17:53 Frank Schacherer [this message]
[not found] <mailman.1071.1070564152.399.help-gnu-emacs@gnu.org>
2003-12-04 23:33 ` GNU Emacs, CVS, DOS and Unix Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=64828F6F9921B040BD700B6C08D8CB8A27DA2B@megehermes.memorecbiotec.de \
--to=frank.schacherer@memorec.com \
--cc=cvs-info@gnu.org \
/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).