Kaz Kylheku wrote:
On Thu, 31 Oct 2002, Steve deRosier wrote:


Here's what is happening:
1. J: is a networked drive connected to my home directory on our Linux
server via Samba
You can't do that, because Linux and Windows don't agree on the
representation of text files.  This affects the treatment of text
documents on update and commit, and also the representation of the CVS/
administrative files.
Also, you should always use native drives both for your sandbox and repository. Generally speaking, networked drives within their native systems (NFS across Unix clones, SMB between Windows boxes) can be considered native. Anything that crosses OS architectures (especially Unix/Windows) is bad.

So even if you solve the location non-transparency problem by using
a CVSROOT that works everywhere, you still have this problem.

New question:  Is there an easy way to fix this problem, so I can
transparently use CVS in the same working directory both remotely and
locally?
This is not a "problem", so much as an architectural fact. Unix and Windows do not agree on what constitutes a text file. It is impossible for them to work together without some sort of intermediary.


/|/|ike




_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Reply via email to