Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
I ran into this when I was modifying the modules file. Since I was learning the syntax of the file. It took me several checkouts/checkins to get it right. Some of these files could potentially grow really large with a lot of stuff that is not worth tracking. Is there any way to test your changes to CVSROOT before committing them? I also want to avoid a user perceiving CVS broken while I'm in the middle of getting it right. How could I avoid this? Thanks, Curt -----Original Message----- From: Tony Hoyle [mailto:tmh at nodomain.org] Sent: Wednesday, December 17, 2003 2:55 PM To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook Subject: Re: [cvsnt] cvswrappers Patrick J Barabe wrote: > Tony, > > thanks for the info. i finally have gotten this to work by checking out > the CVSROOT module of my repository, editing cvswrappers, and committing > it back in (and restarting cvsnt - though i don't really know if that's > necessary). all this using the cvsnt command line client. > To change any file in CVSROOT (except passwd) you have to check it out, modify it and check it back in... nothing will happen if you just change them without doing that. Tony _______________________________________________ cvsnt mailing list cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs