From owner-cvs-user Sun May 4 13:39:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA16042 for cvs-user-outgoing; Sun, 4 May 1997 13:39:26 -0700 (PDT) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA16010; Sun, 4 May 1997 13:39:04 -0700 (PDT) Received: (from eivind@localhost) by bitbox.follo.net (8.7.6/8.7.3) id WAA04526; Sun, 4 May 1997 22:38:38 +0200 (MET DST) Date: Sun, 4 May 1997 22:38:38 +0200 (MET DST) Message-Id: <199705042038.WAA04526@bitbox.follo.net> From: Eivind Eklund To: Bruce Evans CC: cvs-all@FreeBSD.ORG, CVS-committers@FreeBSD.ORG, cvs-user@FreeBSD.ORG, jkh@FreeBSD.ORG, jkh@time.cdrom.com In-reply-to: Bruce Evans's message of Mon, 5 May 1997 06:00:09 +1000 Subject: Re: cvs commit: src/release Makefile References: <199705042000.GAA24412@godzilla.zeta.org.au> Sender: owner-cvs-user@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > >> I use a symlink :-). > > > >Could you please explain this? I can't see how this can solve the > >problem for the cases I mentioned. > > If the sources point to /home/ncvs, then just link /home/ncvs to wherever > the repository is. This requires write permissions to /home of course. This don't solve the problem of reconstructing the CVS information to be able to update from the CVS repository and keep local changes. Changing the repository information is also convenient to be able to work from one repository, and update in another. This is not possible by symlinking /home/ncvs unless you can NFS mount all the hosts together; I've used this (together with ssh) to work locally and commit at freefall. For any listeners that's interested and haven't figured it out yet: Just work from your local CVS tree, and when you want to commit, use the previous shell-script to set the repository to "username@freefall.freebsd.org:/home/ncvs", set CVS_RSH to ssh, and commit. Goes to freefall, just as if you'd logged in there and committed. Eivind.