info-cvs
[Top][All Lists]
Advanced

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

Moving local versions between machines


From: Alain Désilets
Subject: Moving local versions between machines
Date: Fri, 31 May 2002 11:07:32 -0400

I have been using CVS for 3 years now, but have never been able to solve
the following problem. Can anyone help? Thx.

*Problem Description*

I work sometimes from home, sometimes from the office. So I often need
to do the following:

- checkout a module on my office machine
- start modifying it on my office machine
- copy the mopdified module (complete with CVS information) to my home
machine
- finish the modifications on my home machine
- commit the changes from my home machine

But whenever I do this, I find I'm unable to do any cvs commands on the
module that was copied from the office machine.

For example, if I do:

   cvs status

and enter my password, I get:

   /CVSROOTccess /cvsroot/voicecode
   No such file or directory

However, if recopy the module back to the office machine, I find I can
commit the changes, etc... from that machine.

Note that my home CVS setup is OK because the following works:

- checkout a module on my home machine
- do the modifications on my home machine
- commit the changes from my home machine

I suspect the root of the problem is that the module I copy from the
office contains some information about how CVS is setup on the office
machine. When I copy that module to my home machine, this information
becomes invalid because there are slight differences between how CVS is
setup on both machines (e.g. path where CVS is installed).

Is there anyway I can get this to work?

Thanks.

Alain Désilets




reply via email to

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