From owner-freebsd-hackers  Wed Jan 29 17:44:15 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA08896
          for hackers-outgoing; Wed, 29 Jan 1997 17:44:15 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA08891
          for <hackers@freebsd.org>; Wed, 29 Jan 1997 17:44:13 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id RAA11626; Wed, 29 Jan 1997 17:44:08 -0800 (PST)
To: Brian Somers <brian@awfulhak.demon.co.uk>
cc: hackers@freebsd.org
Subject: Re: Source code commits 
In-reply-to: Your message of "Thu, 30 Jan 1997 00:43:57 GMT."
             <199701300043.AAA15572@awfulhak.demon.co.uk> 
Date: Wed, 29 Jan 1997 17:44:07 -0800
Message-ID: <11622.854588647@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> Is it possible to commit source code locally, and get cvsup to send the
> udpates back to freefall ?  If not, would there be a lot of work involved ?

This isn't cvsup's domain, actually, but it is something CVS can
handle itself.  You simply set CVS_RSH to ``ssh' and CVSROOT to
``freefall.freebsd.org:/home/ncvs'', then you do your CVS operations
as normal.

I have some shell functions which I use so that I can keep things
checked out relative to my local CVS repository (and obviously many
times faster than using freefall's) up until the point where I want to
commit the changes, then it fools CVS into thinking that the sources
were originally checked out from freefall too:

function do-local-cvs {
	setenv CVSROOT /home/ncvs
	[ -f CVS/Root ] && echo $CVSROOT > CVS/Root
}

function do-remote-cvs {
	setenv CVSROOT freefall.freebsd.org:/home/ncvs
	[ -f CVS/Root ] && echo $CVSROOT > CVS/Root
}

function cvscommit {
	do-remote-cvs
	cvs commit $*
	do-local-cvs
}