Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
You're right... cvs is good for a specific purpose and not for everything. (I liked the idea of version control over a large set of files, though). Anyway, it turns out that the thing I mentioned on a previous post about tricking a sandbox to use different repositories does not work. Thanx "Bo Berglund" <bo.berglund at telia.com> wrote in message news:1pehr05gonnrgj7bnah6hl5pphb6con0g1 at 4ax.com... > On Thu, 9 Dec 2004 22:53:35 +0200, "mada" <no.spam at no.spam.org> wrote: > > >After some experimentation, I now know that I can use cvsnt server in the > >above scenario, where a server on each machine has a \CVSROOT repository > >configured to X:\repos (see previous post), and therefore, given that the > >removable drive is connected, all commits/updates on both machines are > >performed on the repository on the removable drive. > > > >Also, I found out that I can trick the sandbox on each of the machines to > >additionally commit/update on a local repository, by editing the repository > >\CVSROOT and setting it to a local directory instead of X:\repos. Then, to > >reuse the repository on the removable drive, I reset the server's \CVSROOT > >repository to X:\repos, commit, and go. A bit complicated, but works. > > > >If there is a simpler way to use a sandbox with different repositories > >please tell me. > > If you are anyway carrying the disk between the two PC:s and the only > reason you want to use CVS is that you want to sync the two PC > versions of the files, then why not work on them directly? > Why bother with the CVS usage? > > > /Bo > (Bo Berglund, developer in Sweden)