Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3F58D248.5070000@ece.gatech.edu> Date: Fri, 05 Sep 2003 14:13:28 -0400 From: Charles Wilson Reply-To: cygwin AT cygwin DOT com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Jeffery B. Rancier" CC: cygwin AT cygwin DOT com Subject: Re: Updated: cvs-1.11.6-3 [Requires cygwin-1.5.3+] References: <3F581C4E DOT 5030403 AT ece DOT gatech DOT edu> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Please keep cygwin messages on the cygwin list. Jeffery B. Rancier wrote: > Pardon the ignorance, but does this mean that this must be done on the > repository? And, I don't follow this I may corrupt the repository? > No, it doesn't, exactly. This ONLY affects the modules definition database, and the val-tags database. While the contents of those files are important, they're not your source code. The modules database can always be automatically regenerated from the modules file (this regeneration happens when you check out/check in the modules file. *I'm not sure about this*, but I believe that the val-tags database ONLY helps to speed access to the various tags in the repository, but is not really necessary. I *think* that if you simply delete it, cvs will be somewhat slower for a while, but it eventually will reconstruct the val-tags (it's sort of like a cache) as you continue to use cvs and access old tags. But, we've provided a tool to painlessly fix the problem before it happens -- so why not use it? -- Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/