Date: Fri, 27 Feb 1998 18:27:15 -0700 From: Nate Williams <nate@mt.sri.com> 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 Message-ID: <199802280127.SAA07845@mt.sri.com> In-Reply-To: <199802280111.MAA12608@godzilla.zeta.org.au> References: <199802280111.MAA12608@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> >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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802280127.SAA07845>