Re: question on policy of renaming an extension
| From: | Brad House | Date: | Sun, 20 Jun 2004 15:36:01 +0000 |
| Subject: | Re: question on policy of renaming an extension | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-10649@lists.php.net to get a copy of this message | ||
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