Oops. I did not know that the system only accepts text/plain
attachments. Here is the attachment for TSRM diff. This is in
text format. I will send the diff for the whole project soon.
Thanks,
Ananth.
>>> Derick Rethans <[EMAIL PROTECTED]> 1/29/2004 5:26:01 PM >>>
On Thu, 29 Jan 2004, Ananth Kesa
On Thu, 29 Jan 2004, Andi Gutmans wrote:
> Does everyone concur? :)
I do.
Derick
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Ok with me
On Thu, 29 Jan 2004, Andi Gutmans wrote:
> Does everyone concur? :)
>
> At 10:41 AM 1/29/2004 +0200, Jani Taskinen wrote:
>
> > Like I already commented before, gpc_order:
> >
> > a) confuses (why have two options doing exactly same thing?!)
> > b) has been said to not ev
Does everyone concur? :)
At 10:41 AM 1/29/2004 +0200, Jani Taskinen wrote:
Like I already commented before, gpc_order:
a) confuses (why have two options doing exactly same thing?!)
b) has been said to not even exists since PHP 4
c) can not break BC (variables_order defaults to EG
On Thu, Jan 29, 2004 at 02:07:28PM +0100, Sascha Schumann wrote:
> On Thu, 29 Jan 2004, Patrick Welche wrote:
>
> > On Fri, Jan 23, 2004 at 08:51:16AM +0100, Sascha Schumann wrote:
> > > If you want to propose modifications to the current build
> > > chain, feel free to post a patch.
> >
>
On January 29, 2004 01:01 am, Rasmus Lerdorf wrote:
> Right, that was what I was verifying. I couldn't see any place where a
> reset was done at all, so I thought maybe it was hidden away somewhere.
> Looks like we need to fix that. I'll have a look at it tomorrow.
Already done :).
Ilia
--
PH
On Thu, 29 Jan 2004, Patrick Welche wrote:
> On Fri, Jan 23, 2004 at 08:51:16AM +0100, Sascha Schumann wrote:
> > If you want to propose modifications to the current build
> > chain, feel free to post a patch.
>
> Enclosed is an even nicer patch. I shouldn't have mentioned the "cat"
> warn
On Fri, Jan 23, 2004 at 08:51:16AM +0100, Sascha Schumann wrote:
> If you want to propose modifications to the current build
> chain, feel free to post a patch.
Enclosed is an even nicer patch. I shouldn't have mentioned the "cat"
warning in the previous posting - it has nothing to do with
On Thu, 29 Jan 2004, Ananth Kesari wrote:
>could be to begin working on some simple defects and fix them.
>Can you let me know if I can do that and if yes, how? I mean,
>where to look for the defects filed and what is the procedure to
>start fixing them?
Here are some (longish) urls that list
On Thu, 29 Jan 2004, Ananth Kesari wrote:
> Our changes are spread across many files, so I am not sure if we can
> checkin at this stage of the release of PHP 5.0. Anyway, I have
> attached the diff file for TSRM. Please review the same and give me
> your comments. There are similar changes in oth
Hi,
Our changes are spread across many files, so I am not sure if we can
checkin at this stage of the release of PHP 5.0. Anyway, I have
attached
the diff file for TSRM. Please review the same and give me your
comments.
There are similar changes in other files. If you think I should send
across
th
On Thu, 29 Jan 2004, shimi wrote:
>
> it's not the worms that suck. it's stupid AV vendors that notify an
> address WHICH IS KNOWN TO BE A RANDOM ONE, AND NOT THE VIRUS SENDER that
> "he sent a virus". That's who sucks. Solution: filter mailer-daemons and
> start using return reciepts to know if y
Like I already commented before, gpc_order:
a) confuses (why have two options doing exactly same thing?!)
b) has been said to not even exists since PHP 4
c) can not break BC (variables_order defaults to EGPCS)
It's about time we get really rid of it. When would be better
Isn't this a serious BC break for people who rely on gpc_order and aren't
using variables_order?
Why are you making such a change in a feature freeze?
Andi
At 04:15 AM 1/26/2004 +, Jani Taskinen wrote:
sniper Sun Jan 25 23:15:09 2004 EDT
Modified files:
/php-srcphp.ini-di
14 matches
Mail list logo
