Dubious in this case basically means that CVS has not been used by the various developers on the project consequently there is no confidence in the contents of the repository and the concern is that a developer may get a copy of old code. The code in the production area is what is used to make changes; a personal copy is made, modified, tested and basically put back in production.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark E. Hamilton Sent: Tuesday, August 29, 2006 5:17 PM To: [email protected] Subject: Re: starting over Robert, Huber, Robert wrote: > I have a CVS archive of dubious content and want to start basically from > scratch. First want to save the current archive "just in case" then > clear it out then load it from the code in production. I'm new to CVS > and looking thru the docs I have is not really helping yet. Any > suggestions on how to do what I described above? You didn't find anything describing this because it would rarely be the recommended approach to doing what you want. Why do you describe your repository as dubious? What has happened to make it not reflect what you have in production? The approach to take depends on what you think is wrong and how it got that way, and how your production area was created. -- ---------------- 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 ==================== This email/fax message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this email/fax is prohibited. If you are not the intended recipient, please destroy all paper and electronic copies of the original message. _______________________________________________ info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
