Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86937
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.20 as permitted sender)
Message-ID: <55912BFD.5020005@gmx.de>
Date: Mon, 29 Jun 2015 13:29:01 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Pierre Joye <pierre.php@gmail.com>
CC: PHP internals <internals@lists.php.net>
References: <55905A31.4050302@gmx.de> <CAEZPtU6TbP=QR3kZhm+uPdC8YLfV_vh-P3kOTZyhDJUShzt4tw@mail.gmail.com>
In-Reply-To: <CAEZPtU6TbP=QR3kZhm+uPdC8YLfV_vh-P3kOTZyhDJUShzt4tw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Bundled GD library
From: cmbecker69@gmx.de (Christoph Becker)

Pierre Joye wrote:

> Hi,
> 
> On Jun 29, 2015 3:34 AM, "Christoph Becker" <cmbecker69@gmx.de> wrote:
>>
>> Hi!
>>
>> I've just learned from ext/gd/libgd/README that the bundled GD library
>> is actually a fork of libgd, which was quite a surprise to me as I
>> thought gd is handled similar to pcre and sqlite3.
> 
> It is somehow similar as it was an actual fork before we took over the
> upstream version.
> 
> Due to own BC reasons we cannot be fully synced with upstream at this stage
> but a large part of the library is.

Ah, I see.  Thanks for the explanation. :)

>> Anyhow, I wonder how to deal with bug reports for PHP's gd extension, if
>> they point to a common bug in libgd.  Shall I make PRs against php-src
>> *and* report the issue to libgd?
> 
> Either way. If you can do both it will be fantastic. But as the same
> persons maintain both sides, we do our best to keep them synced :)

Okay, so I'll do both. :)

-- 
Christoph M. Becker