Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:119514
MIME-Version: 1.0
References: <Y+TIlliuIwRyZX8L@swift.blarg.de> <CALKiJKrxkUP_9H+xiw+_=1qh+=4eJhSNNowFToAJDJ7x+FQN2Q@mail.gmail.com>
 <Y+TxnQXFbIzaa+za@swift.blarg.de> <CALKiJKqHCP7=Z8nTWhb5rxQXBSzPX5DPXWNWpoVtovX4Q59M0A@mail.gmail.com>
 <Y+UZyknw0nMZPjkT@swift.blarg.de>
In-Reply-To: <Y+UZyknw0nMZPjkT@swift.blarg.de>
Date: Thu, 9 Feb 2023 16:57:51 +0000
Message-ID: <CALKiJKr9Nrd6o8srgOrqicX+Z598aa_cN7EqC+VArrr_Wzxpvw@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000b3e50805f44748d2"
Subject: Re: [PHP-DEV] How to deal with bugs in vendored libraries?
From: rowan.collins@gmail.com (Rowan Tommins)

--000000000000b3e50805f44748d2
Content-Type: text/plain; charset="UTF-8"

On Thu, 9 Feb 2023 at 16:05, Max Kellermann <max+php@blarg.de> wrote:

> > OK, that seems clear. As far as I can see, this is the first time on this
> > thread or either of the PR threads that you've actually explained that
> > violation.
>
> I explained it already:
>
>  https://github.com/derickr/timelib/pull/141#issuecomment-1386800720
>


Right, I missed that amongst the other comments. Which, again, is why I was
prompting you to clearly summarise the rationale for the change in one
place, to clear up any misunderstandings.

Regards,
-- 
Rowan Tommins
[IMSoP]

--000000000000b3e50805f44748d2--