Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:10649 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 15874 invoked by uid 1010); 20 Jun 2004 15:36:06 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 15075 invoked from network); 20 Jun 2004 15:36:03 -0000 Received: from unknown (HELO nameserver1.mcve.com) (209.251.159.130) by pb1.pair.com with SMTP; 20 Jun 2004 15:36:03 -0000 Received: from mainstreetsoftworks.com (ip68-226-1-214.ga.at.cox.net [68.226.1.214]) by nameserver1.mcve.com (Postfix) with ESMTP id D0CB383D47; Sun, 20 Jun 2004 11:36:01 -0400 (EDT) Message-ID: <40D5AEE1.1080408@mainstreetsoftworks.com> Date: Sun, 20 Jun 2004 11:36:01 -0400 User-Agent: Mozilla Thunderbird 0.5 (X11/20040407) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Derick Rethans Cc: internals@lists.php.net References: <40D5AB1F.7060005@mainstreetsoftworks.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] question on policy of renaming an extension From: brad@mainstreetsoftworks.com (Brad House) heh, well, I know I definitely do not have permissions to do that then :) Any assistance someone could provide me would be appreciated. Also, I can go ahead an make a set of patches to finalize the naming switch for the config.m4/w32 and the remaining references in the code (and commit prior to renaming the directory if desired). Thanks! -Brad Derick Rethans wrote: > On Sun, 20 Jun 2004, Brad House wrote: > > >>The ext/mcve module at some point in time needs to be renamed >>ext/monetra to reflect a naming change, and lessen confusion >>in the field, as the product is no longer referenced as MCVE. >> >>What is the best way to go about doing this? I did not want to >>just go in there and remove ext/mcve and commit the same stuff >>to ext/monetra and 'get in trouble'. (Truthfully, I don't know >>if I even have the perms to do this). > > > The way to do this is: > (on the cvs server): > cp -r mcve montra > > then on the client side with CVS: > > cvs delete mcve > cvs commit mcve (or similar) > > Derick >