Date: Sat, 28 Feb 1998 12:11:04 +1100 From: Bruce Evans <bde@zeta.org.au> To: eivind@yes.no, jkh@time.cdrom.com Cc: cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-CVSROOT@FreeBSD.ORG Subject: Re: cvs commit: CVSROOT avail Message-ID: <199802280111.MAA12608@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>Happens very rarely, actually, since I sync my cvs repository at least >3-4 times a day from freefall. But yes, if I think I'm going to run Here it might take 3-4 days a time :-). Even running remote diffs is too slow to do routinely. I depend on the commit check preventing clobbering of old versions. >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. I use fcvs and lcvs and usually want to run lcvs after fcvs to unthwack it, but often forget. It is almost as inconvenient as directory state. 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. 2) the rcstemplate file is not included in the default log message. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802280111.MAA12608>