-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Craig O'Shannessy <[EMAIL PROTECTED]> writes:
> > The next best solution is to religiously use rsync to update your home > > machine's working directories and then always rsync your @home edits > > back to your work machine for any CVS operations which you'll run by > > logging into your work machine just as you did with 'vi'. > > > > Considered this too, just don't know if I trust myself that much, I've > already lost work once this way. Spose I'm just not that religious. > > > > I'm currently considering sshfs, but the performance won't be > > > good. > > > > Use rsync over ssh! :-) > > > > Wouldn't have done it any other way ;) I suppose you could also consider the Unison File Synchronizer (see http://www.cis.upenn.edu/~bcpierce/unison/ for details) as a way to keep your checked out trees in a consistent state with one another. Enjoy! -- Mark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/zUSz3x41pRYZE/gRAtQmAKDIob1hMY/1VDkVV3pE+DbLvr0RFQCgqjtU G3HEB9tJssRet4rGBA2aeh4= =yis4 -----END PGP SIGNATURE----- _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
