[Top][All Lists]

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

Re: Forcing DOS line endings on checkout/update

From: Noel L Yap
Subject: Re: Forcing DOS line endings on checkout/update
Date: Tue, 31 Jul 2001 12:04:34 -0400

This should be done by the file system (ie Samba)?  For example, if someone vi'd
a file, you'd have the same problem.


|        |                       |
|        |          address@hidden|
|        |          com          |
|        |                       |
|        |          07/31/01     |
|        |          11:35 AM     |
|        |                       |
  |                                                                            |
  |       To:     address@hidden                                             |
  |       cc:     (bcc: Noel L Yap)                                            |
  |       Subject:     Forcing DOS line endings on checkout/update             |

Is it possible to force cvs to use DOS line endings on a Unix-based machine?

I am using  CVSROOT/loginfo  to maintain a local copy which is automatically
update to the HEAD revision when someone does a commit.  This part is
working fine, but the problem is that this "local copy" is really on a SMB
mount point connected to an NT server.  So I'm getting Unix file ending
rather than DOS file endings.  How to I trick cvs into thinking that it is
running in a DOS environment?

This will be eventually used in a production environment, so I would like to
stay away from just running a script to convert the line ending.

Thanks in advance,

Lowell C. Alleman
Martin's Famous Pastry Shoppe

Info-cvs mailing list

This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.

reply via email to

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