[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVS/Vis Studio 6

From: Laine Stump
Subject: Re: CVS/Vis Studio 6
Date: 26 Jun 2001 10:07:31 -0400
User-agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7

"Matt Keyes" <address@hidden> writes:

> I had created several projects under Visual Studio 6 (Vis C++).  I
> imported the ASCII files (i.e. .h, .cpp) to CVS with the following
> command (run from the Linux box... I transferred the files there
> first):
>       cvs import -m "Source Code" Source mkeyes start
> [...]
> Now then, when I checkout the ASCII files and open them under Visual
> Studio 6, I get the following message:
>       Lines ending with only a carriage return detected.
>       These will be modified to include a linefeed.
> Then, as the message states, I get two linefeeds for every one I had
> previously.  When I go back and correct the formatting error, commit
> it, then check it out and look at it again, it looks fine.  However,
> I get the feeling that I might be missing something.  Any help is
> appreciated.

To solve your problem, erase the newly created module from CVS, then
redo the import, but do it from a Windows box.

The problem is that your original files have all lines terminated with
CRLF (as they were created on Windows), and the Unix CVS client does
no translation, so everything goes into CVS with CRLF (in spite of the
fact that the RCS ,v file format is supposed to have just LF for line
termination). Then when you checkout with a Windows client, it

    line of text<CR><LF>


    line of text<CR><CRLF>

(ie it translates the Unix <LF> line ending into Windows <CRLF>).

<obligatory whine>

There are those of us who believe that CVS should be more intelligent
about line ending conventions, but we are squelched by those who
believe that elegance and simplicity of design is more important than
robustness and correct operation (and who apparently never have to do
serious development in a mixed Unix/Windows/Mac environment). Or
something like that ;-) (Yes, I've given up.)

</obligatory whine>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]