Re: CVS on two unconnected machines

[Colby Allred]

I'll make a suggestion, but it may not help, or even work correctly.  I
don't know enough about cvs' disk usage and other underlying functions.

If your repository is small enough, you might be able to mount your zip
disk as a filesystem and have your $CVSROOT point to it. (this is of
course, assuming that you're using some OS that supports mounting
filesystems)  I seem to recall that zip disks/drives have some feature
that you can set some kind of lock that won't let you eject the disk...you
might need to use that.

This implies lots of things that might cause problems...most that i don't
even know of.  Perhaps the guru's on this list can take this idea and
point out its flaws/potential?


On Wed, 21 Feb 2001, Francis Irving wrote:

> On Wed, 21 Feb 2001 10:29:07 -0600, address@hidden (Matthew
> Pressly) wrote:
> 
> >Would it be better to keep the repository on only one machine and just
> >copy working
> >directories back and forth?
> 
> That certainly sounds easier.  You can't ever get it wrong, either.
> 
> The only disadvantage to your current method is that you can't commit
> separate changes separately on the machine which is remote from the
> repository.
> 
> (Saying that, there's no reason you can't make multiple copies of the
> working directory on the remote machine.  Then make separate changes
> to each copy, transfer all the copies back again and commit them
> separately).
> 
> Francis
> 
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
> 

-- 
Colby Allred
Advanced Hardware Architectures
http://www.aha.com/