From owner-cvs-CVSROOT  Fri Feb 27 17:28:09 1998
Return-Path: <owner-cvs-cvsroot>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA15313
          for cvs-CVSROOT-outgoing; Fri, 27 Feb 1998 17:28:09 -0800 (PST)
          (envelope-from owner-cvs-cvsroot)
Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15120;
          Fri, 27 Feb 1998 17:27:43 -0800 (PST)
          (envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
	by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id SAA01189;
	Fri, 27 Feb 1998 18:27:18 -0700 (MST)
	(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
	id SAA07845; Fri, 27 Feb 1998 18:27:15 -0700
Date: Fri, 27 Feb 1998 18:27:15 -0700
Message-Id: <199802280127.SAA07845@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Bruce Evans <bde@zeta.org.au>
Cc: eivind@yes.no, jkh@time.cdrom.com, cvs-all@freebsd.org,
        cvs-committers@freebsd.org, cvs-CVSROOT@freebsd.org
Subject: Re: cvs commit: CVSROOT avail
In-Reply-To: <199802280111.MAA12608@godzilla.zeta.org.au>
References: <199802280111.MAA12608@godzilla.zeta.org.au>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-cvs-cvsroot@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> >I guess it comes down to whether or not you consider thwacking the
> >CVS/Root file easier or the CLI option easier - it's sort of the same
> >to me given that I've been using the aformentioned shell functions for
> >so long that the "stateful model" works for me more than having to
> 
> cvs -d thwacks CVS/Root in -current.  This is often inconvenient.

This is fixed in the most recent version of CVS.  However, the error
handling of client/server mode leaves alot to be desired.  This is on
Cyclic's TODO list of paid work that was due a couple weeks ago, but I
didn't get back to them about the bug until earlier this week.

> BTW, why do the following work differently for remote `cvs commit'?
> Is it because the cvs client is current?
> 1) all files are handled in one batch, even if they are in separate
>    directories.

Optimization to minimize the 'commit' traffic over the wire, and to
minimize the locking.  Doing a 'commit-per-directory' requires more work
than the client is willing to do at this point, and leaves the locks in
place much longer.

> 2) the rcstemplate file is not included in the default log message.

I think you need to checkout the sources from the remote server machine
to get it.  This is stuck in the CVS directory on your clients.


Nate