Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 67753 invoked by uid 500); 9 Jul 2000 21:26:54 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 67735 invoked from network); 9 Jul 2000 21:26:53 -0000 Message-ID: <3968F158.711973D8@Golux.Com> Date: Sun, 09 Jul 2000 17:40:40 -0400 From: Rodent of Unusual Size Organization: The Apache Software Foundation X-Mailer: Mozilla 4.72 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: new-httpd@apache.org Subject: Re: Did we ever decide how to move files around? References: <20000705022022.M29590@lyra.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Greg Stein wrote: > > There are two ways to move a file around: > > Method 1: > *) locus: cp old/file.name,v new/file.name,v > *) client: cvs del old/file.name > *) client: delete all tags on new/file.name > > Method 2: > *) client: cp old/file.name new/file.name > *) client: cvs add new/file.name > *) client: cvs del old/file.name I prefer method 2 for its simplicity, but it makes it a right bugger to track down why something was changed before the move. You're wholly dependent on a) the person who did it correctly specifying the full and correct path for old/file.name, and b) remembering to look at the log for rev 1.1 to find out from whence the file came. So, on the whole, I prefer method 1. -- #ken P-)} Ken Coar Apache Software Foundation "Apache Server for Dummies" "Apache Server Unleashed"