CVS For Modem Users? 5
David Symonds asks: "CVS is great if you can commit after each significant change; however, if you have limited access (e.g. a dialup connection), this tends to make things sloppy. Are there any "CVS proxies" that can cache CVS commits locally, then send them on to the CVS server when you next connect to the Net?"
Commit early, commit often (Score:1)
In general there are a few thing to make remove CVS over slower connections a bit better. While not always possible, $(subject) is a good idea (making large commits into smaller commits). In addition, using the -z (compression) option (say, -z3 or -z4) can make commits much faster over slower. Of course, working/committing on a remote box with a fast connection also works
Not a very good idea (Score:3)
It seems to me that it's more a matter of how you use CVS. Why not just commit all changes when you are connected, instead of trying to put together another application to do it for you?
cvsq (Score:4)
here [volny.cz]
Instead of "cvs commit" you use "cvsq commit". Later, when you are online, you type "cvsq upload" to cause the queued commits to get pushed to the CVS server.
Use rsync (Score:1)
latest downloads from the CVS repository, but don't want to wait. When I still had a Linux box handy, I had it rsync to the CVS repository at midnight every day, and then when I wanted to update, I did it from my local mirror instead of over the wire.
YMMV.
Bitkeeper? (Score:1)