From: "Stefan Monnier <foo@acm.com>" <monnier+gnu.emacs.help/news/@flint.cs.yale.edu>
Subject: Re: After cvs, emacs does not encode file correctly as dos
Date: 17 Sep 2002 09:17:10 -0400 [thread overview]
Message-ID: <5lfzw8pxgp.fsf@rum.cs.yale.edu> (raw)
In-Reply-To: m2bs6wpyzv.fsf@mmynsted.corp.vha.com
> You are correct. I had a line in my cvs controlled file, that
> contained the cvs key word $Log$. That key word was automatically
> substituted with the cvs log for that file during the normal course
> using cvs to manage the file. Part of that "log" section, supplied by
> cvs, did not contain a ^M character at the end of the line.
You might want to check gnu.cvs.help to see why it happened and how
to make sure it won't happen again.
Stefan
next prev parent reply other threads:[~2002-09-17 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 13:41 After cvs, emacs does not encode file correctly as dos Mark Mynsted
2002-09-10 13:49 ` Kai Großjohann
2002-09-16 13:07 ` Mark Mynsted
2002-09-16 13:54 ` Kai Großjohann
2002-09-17 12:44 ` Mark Mynsted
2002-09-17 13:17 ` Stefan Monnier <foo@acm.com> [this message]
2002-09-18 12:46 ` Mark Mynsted
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=5lfzw8pxgp.fsf@rum.cs.yale.edu \
--to=monnier+gnu.emacs.help/news/@flint.cs.yale.edu \
/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).