[Top][All Lists]

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

RE: Forcing DOS line endings on checkout/update

From: Frederic Brehm
Subject: RE: Forcing DOS line endings on checkout/update
Date: Wed, 1 Aug 2001 11:45:51 -0400

 > From: Alleman, Lowell [<mailto:address@hidden>mailto:address@hidden
 > Subject: RE: Forcing DOS line endings on checkout/update
 > > From:       address@hidden [SMTP:address@hidden
 > > Subject:    Re: Forcing DOS line endings on checkout/update
 > With CVS You have two, and exactly two, viable,
 incompatible, options:
 >    SYSTEMS!!!!!!  (that's one of the reasons CVS has client/server
 >    support in the first place, ya know!)

Lookout, the world's going to end, but for once I agree with Mr. Woods. Maybe not his style of presenting it, but the content makes sense. Working directories should never be shared.

 > I'm not making a "WORKING" directory.  The "shared" copy will
 > end up on a NT

It seems like the request in the original message
has been forgotten somewhere in this thread.

I think that Mr. Alleman wants to keep a checked-out copy as described in
but with an additional wrinkle: DOS line endings on some files.

The CVS manual section suggests that the loginfo file have something like

^cyclic-pages (date; cat; (sleep 2; cd /u/www/local-docs; cvs -q update -d) &) >> $CVSROOT/CVSROOT/updatelog 2>&1

Maybe all that he needs to do is to replace the cvs command with a
script that does the cvs command followed by a unix2dos on all the
files that must be in DOS format. He might need to use an
intermediate temporary directory to insure that the checked-out copy
always has files with the right characteristics.

Is that so hard?

Fred Brehm, Sarnoff Corporation, address@hidden

reply via email to

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