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
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
>
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 ren
On Sun, 20 Jun 2004, Brad House wrote:
> 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 remaini
Hi,
On 20 Jun 2004, at 17:36, Brad House wrote:
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 des
Why not take the opportunity and move the extension to PECL?
It sounds like a good candidate.
Well, PECL still seems a bit like the redheaded step-child. I cannot
even seem to reference it in the php documentation online (except for
seeing some modules have been moved there).
There are quite a few
On Sun, 20 Jun 2004, Brad House wrote:
> Well, PECL still seems a bit like the redheaded step-child. I cannot
> even seem to reference it in the php documentation online (except for
> seeing some modules have been moved there).
> There are quite a few users that utilize this extension, including
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 20 Jun 2004, at 19:42, Brad House wrote:
When PECL is better adopted by the community, and PHP provides
documentation on them, I would have no problem moving it there.
Following Rasmus' mail, moving your extension also increases
the convenience f
Please don't associate being moved to PECL with whether or not the
extension is distributed as a standard PHP extension in the distribution
tarball or not. The two have nothing to do with each other.
-Rasmus
On Sun, 20 Jun 2004, Jan Lehnardt wrote:
> --[PinePGP]-
I was under the impression that it was one or the other, not
both. How do you coordinate the 2?
-Brad
Rasmus Lerdorf wrote:
Please don't associate being moved to PECL with whether or not the
extension is distributed as a standard PHP extension in the distribution
tarball or not. The two have noth
On Sun, 20 Jun 2004, Brad House wrote:
> I was under the impression that it was one or the other, not
> both. How do you coordinate the 2?
At distribution time we select which extensions to bundle. Generally ones
we decide belong in the distribution tarball get a cvs symlink from
php-src to pe
Actually I think the best way is to rename the directory in the repository
as it would save history.
At 10:36 AM 6/20/2004 -0400, Brad House wrote:
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 g
On Tuesday 22 June 2004 13:03, Andi Gutmans wrote:
> Actually I think the best way is to rename the directory in the repository
> as it would save history.
That would break the checkout of the older php versions. The directory needs
to be copied and then cvs delete the files in the old one.
Edin
13 matches
Mail list logo
