A little simpler would be a forced commit (cvs commit -f) of a key file in CVSROOT
~Matt -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark E. Hamilton Sent: Friday, March 03, 2006 2:50 PM To: [email protected] Subject: Re: Rebuilding administrative file database Ted Stern wrote: > On 02 Mar 2006 14:34:24 -0800, Mark E. Hamilton wrote: > >>Is there a way to force a rebuild of the $CVSROOT/CVSROOT >>administrative files without doing a commit? For instance, if someone >>removes the taginfo file is there a way to do the equivalent of a 'cvs >>update -C' in that directory to refresh it (or all of them)? > > > You could checkout CVSROOT somewhere, then copy the taginfo file back > into $CVSROOT/CVSROOT. Yes, that would work. I've nearly 200 repositories, and though I could write a script to do this I was hoping for a more elegant way. I also wanted to be sure to hit all the config files; I was just using taginfo as an example. -- ---------------- Mark E. Hamilton Orion International Technologies, Inc. Sandia National Laboratory, NM. 505-844-7666 _______________________________________________ Info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
