-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
attached are just a few one-line changes to the current README.CVS-RULES
files in 5.2 and HEAD, maybe it needs even more massaging.
- - Markus
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.2 (MingW32)
Comment: Using GnuPG with Mozilla - htt
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hi Markus,
| +PHP_4_4 Is used to release the PHP 4.3.x series. Only bugfixes are
| permitted
| on this branch.
Should that be "Is used to release the PHP 4.4.x series"?
Jasper
Markus Fischer wrote:
> Hi,
>
> attached are just a fe
Hello Markus,
updated in 4.3, 4.4, 5.0, 5.1, 5.2 and HEAD :-)
best regards
marcus
Sunday, May 21, 2006, 10:40:17 AM, you wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> Hi,
> attached are just a few one-line changes to the current README.CVS-RULES
> files in 5.2 and HEAD, maybe it
Hello Moritz,
Sunday, May 21, 2006, 2:22:46 AM, you wrote:
> I will correct the ZTS stuff, although ZTS should not be needed for this
> sapi if I understand it correctly?
Yes, you could make use of it by providing your own context that stores
everything you have right now in global variables. On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[sorry for sending twice, Marcus, gone through wrong list email]
Hi,
I expected this to be bogusfied. The thing is ... if you put a normal
string for a %d it just works. Now that people learn about __toString()
I think it's not clear why %d doesn't w
Hello Markus,
Sunday, May 21, 2006, 12:54:37 PM, you wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> [sorry for sending twice, Marcus, gone through wrong list email]
> Hi,
> I expected this to be bogusfied. The thing is ... if you put a normal
> string for a %d it just works. Now th
