On Tue, Jul 30, 2019 at 6:15 PM Johannes Schlüter
wrote:
> On Tue, 2019-07-30 at 13:28 -0400, Bishop Bettini wrote:
> > On the other, I've found it refreshing working in a
> > slender repo that doesn't have all the history and process rules.
> > This is good for external (non-core and non-extensi
On Tue, 2019-07-30 at 13:28 -0400, Bishop Bettini wrote:
> On the other, I've found it refreshing working in a
> slender repo that doesn't have all the history and process rules.
> This is good for external (non-core and non-extension) collaborators,
> particularly allowing write access to those wh
Hi!
> This is good for external (non-core and non-extension) collaborators,
particularly allowing write access to those who wouldn't want or need
write access to engine code.
Yes, in theory. In practice I don't see too many of those flocking to
it, unfortunately. As for process, I think we have e
On Sun, Jul 28, 2019 at 8:48 PM Stanislav Malyshev
wrote:
>
> As you probably know, we've been running PHP fuzzing under Google's
> OSS-Fuzz[1] project for a while now (and found and fixed some bugs due
> to it).
>
> This has been enabled by the PHP fuzzing API SAPI[2] which currently
> lives in
On Mon, Jul 29, 2019 at 2:48 AM Stanislav Malyshev
wrote:
> Hi!
>
> As you probably know, we've been running PHP fuzzing under Google's
> OSS-Fuzz[1] project for a while now (and found and fixed some bugs due
> to it).
>
> This has been enabled by the PHP fuzzing API SAPI[2] which currently
> liv
Hi!
As you probably know, we've been running PHP fuzzing under Google's
OSS-Fuzz[1] project for a while now (and found and fixed some bugs due
to it).
This has been enabled by the PHP fuzzing API SAPI[2] which currently
lives in a separate repository. Since the setup is working pretty well
for a
