On 01/27/2012 05:49 PM, Clint M Priest wrote:
> I'm trying to upload the latest getters/setters patch to:
> https://bugs.php.net/bug.php?id=49526
>
> I get "Uploaded file is empty or nothing was uploaded."
>
> Is there a problem or a file size limit? The patch file is 205k now.
Really, a 200k
I'm trying to upload the latest getters/setters patch to:
https://bugs.php.net/bug.php?id=49526
I get "Uploaded file is empty or nothing was uploaded."
Is there a problem or a file size limit? The patch file is 205k now.
-Clint
Ok, by popular demand I have changed "Bogus" to "Not a bug" in the bugs
tracker. The sub-status stuff we have been discussing can just be added
in the comment when you mark something as "Not a bug". eg.
Status: Not a bug
Reason: 583 CNR
So, having done this, for the folks too skittish to mark stu
Hi internals!
I added a patch for https://bugs.php.net/bug.php?id=52719, which fixes
the crash / memleak. All tests run fine (apart from those that always
fail).
I think the patch could be applied to all branches, but not sure
whether it is critical enough to land on 5.4 now or whether I should
w
Some may also read the execve() linux man page.
It has hints about argument parsing and shebangs :)
http://linux.die.net/man/2/execve
Julien.P
2012/1/26 Ángel González
> On 26/01/12 11:35, Kiall Mac Innes wrote:
>
>> Surely you can detect which operating system you're running on, and have
>> P
Personally I would want to have an audit log of emails on production. That
actually is probably more important to me than non-production environments :)
On Jan 27, 2012, at 1:37 AM, Martin Jansen wrote:
> Is there any intention behind enabling the mail.add_x_header
> configuration directive in
Is there any intention behind enabling the mail.add_x_header
configuration directive in php.ini-production?
http://lxr.php.net/opengrok/xref/PHP_TRUNK/php.ini-production#1018
This setting exposes (sort of) sensitive information about application
deployments to third parties while IMO having no ap
