Hi!
On 11 Jul, 2014, at 4:29 pm, Stas Malyshev wrote:
> Hi!
>
>> And while I was trying to figure out what does that mean, or why should
>> that prevent the travis build, I've just remembered that we don't allow
>> travis builds for PHP-5.3 and PHP-5.4 branches:
>> http://git.php.net/?p=php-src
On Fri, Jul 11, 2014 at 10:58 AM, Stas Malyshev
wrote:
> Hi!
>
> > mentioned a few times now), and I think this will cause a significant
> > amount of pain for the people who wanna merge pull requests after the
> > phpng (or other similar major rewrite) is merged to the master, as they
> > will b
Hi!
> mentioned a few times now), and I think this will cause a significant
> amount of pain for the people who wanna merge pull requests after the
> phpng (or other similar major rewrite) is merged to the master, as they
> will be required to backport the changes.
When we will have the major rew
On Fri, Jul 11, 2014 at 10:29 AM, Stas Malyshev
wrote:
> Hi!
>
> > And while I was trying to figure out what does that mean, or why should
> > that prevent the travis build, I've just remembered that we don't allow
> > travis builds for PHP-5.3 and PHP-5.4 branches:
> >
> http://git.php.net/?p=ph
Hi!
> And while I was trying to figure out what does that mean, or why should
> that prevent the travis build, I've just remembered that we don't allow
> travis builds for PHP-5.3 and PHP-5.4 branches:
> http://git.php.net/?p=php-src.git;a=blob;f=.travis.yml;h=f1a333adcb3e6c35f3fe19c27fbd7a28d99fe
On Fri, Jul 11, 2014 at 9:22 AM, Tjerk Meesters
wrote:
> Hi guys,
>
> After making another commit into my ucwords() pr and waiting for an hour
> or so I noticed that Travis CI hasn’t picked it up yet; in fact, the
> previous commit wasn’t picked up either.
>
> Other pr’s that were created before
