On 2015-02-05, Dmitry Stogov wrote:
> --001a11c20e52da1ee0050e556679
> Content-Type: text/plain; charset=UTF-8
>
> Hi Yasuo,
>
> Following our conversation, I tried to imagine how DbC should look like in
> PHP from user perspective. Finally, I was influenced by the semantic
> proposed in D, and sy
On 2014-10-26, Bob Weinand wrote:
>> Am 26.10.2014 um 17:23 schrieb Lester Caine :
>>
>> On 26/10/14 15:41, Bob Weinand wrote:
>>> Ask them at PhpStorm. They were pleased to not have to use DBGp for it.
>>> They just initially requested it because they didn’t knew any better
>>> protocol. That’s
On 2014-08-15, Pierre Joye wrote:
> --001a1133979e094b370500b2c0a9
> Content-Type: text/plain; charset=UTF-8
>
> On Aug 16, 2014 12:20 AM, "David Soria Parra" wrote:
> (didn't
>> we learn anything from PHP 6?).
>
> I did. And with opcache. Both with h
On 2014-08-15, Ferenc Kovacs wrote:
> --001a11c1258a38c82a0500a8b070
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
> we don't have a single instance where we were able to deliver a minor
> release under a year, and I'm fairly sure that 7.0 will see more pr
On 2014-08-12, Sara Golemon wrote:
> On Tue, Aug 12, 2014 at 10:08 AM, Andrea Faulds wrote:
>> On 12 Aug 2014, at 17:53, Sara Golemon wrote:
>>> Voting is open: https://wiki.php.net/rfc/switch.default.multiple#vote
>>
>> I’m all for this, but the *minimum* discussion period is *two* weeks.
>>
>
On 2014-07-25, Andrea Faulds wrote:
>
> On 25 Jul 2014, at 18:02, Nikita Popov wrote:
>
>> I think the main question here is whether MSVC will have good C99 support
>> by the time PHP-Next is released. The other major compilers (GCC, Clang,
>> Intel) may not support all of C99 (esp stuff like FP
Am 7/21/14, 10:21 PM, schrieb Yasuo Ohgaki:
>
> Even if we have PHP-5.7 branch, we have merge up policy. Therefore,
> any new feature will end up with master, I suppose. If a new feature is
> only available to PHP-5.7 branch, it's a merge bug, isn't it?
>
> Regards,
We had this policy before
On 2014-07-21, Michael Wallner wrote:
> --001a11345984e013cd04feb0d9a1
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
>
> On 21 Jul 2014 10:21, "Julien Pauli" wrote:
> PHP-Next.
>
> I don't think that a cleanup is nearly as important as php-ng is as we
> s
Lazare Inepologlou schrieb:
> I use anonymous classes very frequently in Java and in C#, and I would say
> that they are quite useful. However the examples given in the RFC are
> really bad ones. Why on earth would you need a constructor for an anonymous
> class? Anonymous classes are used to impl
John Stokes schrieb:
> I'm working on documenting the XMLReader and XMLWriter classes. Is there
> someone on the list that can answer some questions about the details of
> how XMLReader works?
Please don't ask to ask. Sent a mail to this list or to the php.doc
mailinglist and just ask your quest
We have recenty discussed a lot of new language features and RFC while our
github pull requests are continously growing without getting pulled. We
have 74 open pull request.
So this is a clal for participation in helping to wingle those numbers
down. If you have karma and can review open changes p
Florin Patan schrieb:
> - lack of clear documentation about the internals: you really can't
> tell me that the docs out there are clear because I did a bunch of
> searching for them and I'm pretty good at finding stuff
You are welcome to improve the documentation and make it easier for
people to
On 2013-08-27, Lior Kaplan wrote:
> --089e01175f31fb193804e4f1a4bf
> Content-Type: text/plain; charset=UTF-8
>
> Hi,
>
> I'm please to say that we keep processing the requests faster and faster,
> leaving only few not handled in their first week. Thanks for everyone who
> helped.
>
Again thanks fo
On 2013-06-25, Ferenc Kovacs wrote:
> there were some initial discussion and work done on moving the docs to git,
> see
> https://wiki.php.net/doc/git
> http://git.php.net/?p=3Dweb/doc-editor.git;a=3Dshortlog;h=3Drefs/heads/GIT_=
> READY
> http://marc.info/?l=3Dphpdoc&m=3D132321958514090&w=3D2
>
>
On 2013-06-19, Johannes Schl�ter wrote:
> Hi,
>
> As the release of PHP 5.5.0 is imminent it is time to implement the
> decision about PHP 5.3's EOL.
>
> In https://wiki.php.net/rfc/php53eol it was decided that PHP 5.3 should
> go into "security only" mode once PHP 5.5 was released. As PHP 5.3.27
On 2013-06-19, Johannes Schl�ter wrote:
> Good bye 5.3, you were a great step for PHP!
> Looking forward to a bright and open future!
Thank you for taking care of this branch for so long. Keep the good
job up.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http:/
Hi Anatol,
I saw your commit 74555e7c26b2c61bb8e67b7d6a6f4d2b8eb3a5f3 added a 4mb
mp3 file. Is it possible to create a much smaller mp3 that helps to
reproduce the same bug? The file blows up the taball file for the final
release, which I hope to keep as small as possible.
Thanks in advance,
Davi
On 2013-05-17, Remi Collet wrote:
> --030306010103010609050002
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 7bit
>
> Hi,
>
> I plan to allow php-fpm to be aware of systemd and so, use the
> type=notify mode.
>
> I'd like to apply to attached patch to 5.4 and 5
On 2013-04-25, Stas Malyshev wrote:
> Hi!
>
>> Shouldn't we
>>
>> Keep CURL_WRAPPERS_ENABLED defined to 0 ?
>>
>> or remove it from PHP-5.4 before 5.4.15 ?
>> (was not included in any "official" version yet)
>
> Since the wrappers are gone, I think we should just drop it. If I don't
> hear any o
Hi Sarah,
Hi Ben,
ext/standard/tests/array/array_column_object_cast.phpt is failing on
PHP-5.5. I bisected to:
1a03bd5dee97a0f8b9e74b7f8db5231abd8cc7e4 is the first bad commit
commit 1a03bd5dee97a0f8b9e74b7f8db5231abd8cc7e4
Author: Sara Golemon
Date: Mon Apr 22 14:57:05 2013 -0700
Allow a
On 2013-04-17, Pierrick Charron wrote:
> --001a11c37cdc78c2e304da95cfde
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi folks,
>
> I just opened a vote for the curl-wrappers removal in 5.5. Since we are in
> a tight schedule, the vote duration will only be a week and will end April
> 24th.
>
On 2013-04-12, Johannes Schl�ter wrote:
> 5.3 users might depend on some part of the behavior and have learned to
> live with bugs. We shouldn't kick "features" at this stage.
curlwrappers should definatly stay in 5.3 and 5.4. I have no problem
with having them removed in 5.5 (with an RFC) but I
On 03/27/2013 09:35 PM, Pierre Joye wrote:
> We have done that many times in the past for 5.3 and 5.4. It is
> relatively risk free. Even more for 5.5 during beta phase. It does not
> add new features but fixes bugs.
>
> The good side effect is that we can test it well with 5.5 and back
> port to
On 2013-03-26, Ond?ej Sur? wrote:
> --bcaec548a7f385895a04d8d51fce
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
>
> Hi,
>
> I am trying to build PHP 5.5beta1 with clang, so the question is:
>
> Would you be interested in the results? This would be one sho
On 03/26/2013 11:44 PM, Anatol Belski wrote:
> What +/- I personally see upgrading this at this time:
>
> contra:
> - there might be bugs, the next release might have not all them fixed
> - 5.11 is what the latest linux exts have even as dev
> - older/custom magic files might be incompatible
>
>
Hi Internals,
I added the default Zend OPCache settings to php.ini-development and
php.ini-production atm. To have more people testing the opcache I would
like to enable the OPCache in php.ini-development during the beta phase
and disable it once we start the first RC. I hope we catch more errors
On 03/20/2013 01:51 AM, Stas Malyshev wrote:
> Hi!
>
>> as you are aware we delayed the first beta by about 4 weeks to get
>> Zend Optimizer in. This week will finally see the release of the first
>> beta. This implies:
>>
>> No new features should be added to the PHP-5.5 branch from now on!
>>
Hi Internals,
as you are aware we delayed the first beta by about 4 weeks to get
Zend Optimizer in. This week will finally see the release of the first
beta. This implies:
No new features should be added to the PHP-5.5 branch from now on!
RFC that are currently in voting phase can be merged on
On 03/07/2013 10:33 PM, Philip Olson wrote:
>> I think the only thing requiring a 2/3 vote would be the decision on
>> wheather to enable it by default or not. As long as it's in ext/
>> and not enabled a 50% should be sufficient.
>
> Shouldn't we be focusing on how this makes PHP better? And not
Hi Internals,
PHP 5.5.0 Alpha 6 has been released for testing. As you know we were
supposed to release a first beta but due to the current voting on ZO+
we went for yet another alpha. This time, it's the last one.
The packages can be found at:
http://downloads.php.net/dsp
and windows packages
On 2013-03-07, Rasmus Lerdorf wrote:
> On 03/07/2013 09:01 AM, Anthony Ferrara wrote:
>
>> So my proposal is to slow down for a minute and not call this RFC
>> accepted or not until we can come to some consensus as to if it
>> classifies as a language change or not... Better to clarify for the
>>
On 2013-02-27, Zeev Suraski wrote:
> On 27 2013, at 18:58, Anthony Ferrara wrote:
>
>> Zeev et al,
>>
>> I just want to put my justification for the "only if no delay" vote. I voted
>> that way because we're already at a significant delay. If this vote was a
>> month ago when O+ was sugges
On 2013-02-21, Rasmus Lerdorf wrote:
> Personally I would love to see more RFCs focusing on performance and
> less on syntax changes. Of course, a syntax change RFC, and even the
> initial (often shaky) implementation of a syntax-related change is much
> much easier to whip up than the deep analys
On 2013-02-19, Stas Malyshev wrote:
> Hi!
>
>> echo date_create('@1361240634')->format('Y-m-d');
>> // output: 2013-02-19
>>
>> echo date('Y-m-d',1361240634);
>> // output: 2013-02-18
>
> timestamp dates are created with UTC TZ, date() assumes your configured TZ.
I ran into this myself and I per
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
so just to make this sure. We are NOT skipping the RFC. we are
planning to merge it before beta1 IN CASE the RFC get's accepted. I
believe a op cache is really important for the overall acceptance so I
hope the RFC gets accepted. Nevertheless it's
On 2013-01-29, Zeev Suraski wrote:
> --e89a8fb1f5b0f501b204d468d53f
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
>
> All,
>
>
>
> Following the discussion at the end of last week, I prepared a draft RFC
> for the inclusion of Optimizer+ in PHP.
>
> In par
On 2013-01-28, Zeev Suraski wrote:
> --e89a8fb1fbd85c066a04d455d2d7
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
>
>
> The specific case in point is
> https://wiki.php.net/rfc/propertygetsetsyntax-v1.2 - which while has more
> supporters than opposers, co
Hi Internals,
as you might have read in the 5.5.0alpha4 announcments, we are moving
forward with 5.5.0. We are already a bit late on the schedule and
we want to begin the beta cycle in 14 days and concentrate on QA
for the 5.5.0 release from now on.
This includes a feature freeze. No new features
On 2013-01-19, Xinchen Hui wrote:
> Commit:f7b99c481d0a943d922e99ad9afa82c45193030e
> Author:Xinchen Hui Sat, 19 Jan 2013 17:01:57
> +0800
> Parents: e23fca8910b96f1c3bb26c6582c17c92fd6f2f7a
> Branches: PHP-5.5
>
> Link:
> http://git.php.net/?p=php-src.git;a=commitdiff;
On 2013-01-18, Stanislav Malyshev wrote:
> Commit:33b104c778c5c0e5446671397aaddd66efa4a7bc
> Author:Stanislav Malyshev Mon, 14 Jan 2013
> 00:06:09 -0800
> Parents: f63a9f6c11c05aa76158b6cae0e05340d303a6af
> Branches: PHP-5.3 PHP-5.4 PHP-5.5 master
>
> Link:
> http://git
On 2013-01-09, Rasmus Lerdorf wrote:
> On 01/09/2013 04:16 AM, Derick Rethans wrote:
>> On Tue, 8 Jan 2013, Rafael Dohms wrote:
>
>>> 1. The syntax is crap: this is solvable, let's find the right syntax
>>
>> Any extra syntax makes the PHP parser more complicated (and arguably
>> slower). I don'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Internals,
I think with the start of recent 5.3 EOL discussion, it's about time
to give an overview over the 5.5 schedule as far as I planned it.
I want to go for a new alpha this week (on thursday), 4 week after the
first one. I should have send
On 2012-12-05, Sara Golemon wrote:
> remote: Welcome pollita.
> remote: Changesets accepted. Thank you for your contribution.
> remote:
> remote: Attempting to push to mirror g...@github.com:php/php-src.git
> remote: Write failed: Broken pipe
> remote: fatal: The remote end hung up unexpectedly
>
On 2012-12-06, Sebastian Bergmann wrote:
> I brought this up on #php.pecl yesterday and David already investigated
> a bit but I thought I should probably bring this up here as well.
>
> I cannot build PHP-5.5 with --enable-dtrace on Fedora 17, details are
> here: https://gist.github.com/42142
On 2012-11-15, "d...@php.net" wrote:
> Hi Internals,
>
> as announced a few weeks ago, we tagged PHP 5.5.0alpha1 on Tuesday. This
> release marks the start of 5.5.0 release process.
>
> The packages can be found at:
>
> http://downloads.php.net/dsp
>
Windows builds are up at
http://windo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Makes sense, I'll bumped the version to 5.6.0-dev
On Tue 13 Nov 2012 08:23:31 PM CET, Derick Rethans wrote:
> On Tue, 13 Nov 2012, Johannes Schlüter wrote:
>
>>
>>
>> On Nov 13, 2012, at 18:44, David Soria Parra
Hi Internals,
with the first alpha going to be tagged today and officially released
on Thursday, I went ahead and created the 5.5 branch. Merging should
be still straight forward, but it's going to be 5.3 -> 5.4 -> 5.5 ->
master.
I know this is a mess, but I think we'll have to live with that fo
On 2012-11-13, Adam Harvey wrote:
> On 13 November 2012 01:16, Ferenc Kovacs wrote:
>> On Mon, Nov 12, 2012 at 4:00 PM, Ulf Wendel wrote:
>>> Don't bother. There is a standard way of deprecation, at least I assume
>>> there is. Its proven. Use it: docs warnings, E_DEPRECATED, remove.
>>
>> I agr
, 2012 at 7:45 PM, Sherif Ramadan wrote:
>
>> On Fri, Nov 2, 2012 at 11:21 AM, David Soria Parra wrote:
>>> Hi Internals,
>>>
>>> I was asked to send heads up before pushing an RC, so here we go: As we
>>> were a bit busy this week we had to postpone the RC
Hi Internals,
I was asked to send heads up before pushing an RC, so here we go: As we
were a bit busy this week we had to postpone the RC to next Tuesday.
So 5.4.9RC1 will be tagged on Tuesday and released on Thursday. 5.4.9
final will be tagged on 2012-11-19 and released on the 22th.
As I am fo
On 2012-09-17, Sebastian Bergmann wrote:
> Am 17.09.2012 17:36, schrieb Johannes Schl?ter:
>> There are very few special processes. In fact the only RM-specific
>> things are around packaging the tarballs up, while that's described in
>> an README.
>
> Does this have to be manual process? Is ther
On 2012-09-08, David Soria Parra wrote:
> Hi internals,
> I would like to go ahead and propose Julien Pauli as the RM for 5.5. He
> is an active member of the PHP.net community, has deep knowledge of
> the internals and the necessary backing from his company to be able to
> de
On 2012-09-08, Pierre Joye wrote:
> Hi!
>
>
> On Sep 8, 2012 1:49 PM, "David Soria Parra" wrote:
>
>> As most people know we do not include patches in 5.4 that will break
>> backwards compatibility.
>
> We do not include them anywhere in any future 5.x
Hi internals,
it's been a great eight months now for PHP 5.4. We released 5.4.0 final
in february and since then we were able to deliver a new PHP version
every month (thanks to the hard work from stas).
As most people know we do not include patches in 5.4 that will break
backwards compatibility.
ng is broken.
If no critical issues is found in this RC, the final version will be
released in two weeks.
Regards,
Stas Malyshev and David Soria Parra
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hello!
The PHP Development Team announces the immediate availability of PHP
5.4.6 and PHP 5.3.16. The releases fixes over 20 bugs.
All users are adviced to update to PHP 5.4.6! Alternatively, PHP 5.3.16
is recommended for those wishing to remain on the 5.3 series.
PHP 5.4.6:
Release Announc
Hello!
The PHP Development Team announces the immediate availability of PHP
5.4.5 and PHP 5.3.15. The releases fixes a security issue in the stream
implementation and over 30 bugs.
All users are adviced to update to PHP 5.3.15 or PHP 5.4.5!
PHP 5.4.5:
Release Announcement: http://www.php.ne
Hello!
The PHP Development Team announces the immediate availability of PHP 5.4.4
and PHP 5.3.14. The releases two security related issues and over 30 bugs.
The release fixes two security issues: A weakness in the DES
implementation of crypt() and a heap overflow issue in the phar extension.
Al
On 2012-06-03, Yasuo Ohgaki wrote:
> Hi,
>
> I noticed that old PHP source in git lacks Zend directory.
> Perhaps, all Zend Engine 1?
>
> php-4.4.9 tag
> http://git.php.net/?p=php-src.git;a=tree;h=43c2df47e3782bcc0975f165b77fde40daa96b14;hb=a4d3a4d2ca89c80f37dca11a4e0eee1ef187ba18
>
> php-4.3.11 t
On 2012-06-03, Yasuo Ohgaki wrote:
> Hi,
>
> I noticed that old PHP source in git lacks Zend directory.
> Perhaps, all Zend Engine 1?
Thanks i'll take a look
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Going through the 26 open pull requests (please let us work on getting
that number down), I stumbled over https://github.com/php/php-src/pull/60.
This was already proposed on the mailinglits, but the thread died fast without
a satisfying answer on whether to add a function boolval() or not.
Perso
Hi!
We would like to announce the second RC of the 5.4.4 version. This
is mainly a bugfix release. The release includes a fix for a weakness
crypts() DES implementation (CVE-2012-2143). Please test it and notify
us of any problems you may encounter. The full list of the fixes is as
always in the
Hello!
The PHP Development Team announces the immediate availability of PHP
5.4.3 and PHP 5.3.13. The releases fix security related issues in a
previous attempt to fix a CGI vulnerability (CVE-2012-2311).
PHP 5.4.3 also contains a fix for a buffer overflow vulnernability in
apache_request_headers
Hello!
The PHP Development Team announces the immediate availability of PHP
5.4.1 and PHP 5.3.11. The releases fix security related issues in the
name validation of uploaded files and the handling of open_basedir in
the readline extension. Support for Apache 2.4 was added and over 60
bugs were fix
On 2012-04-17, Stas Malyshev wrote:
> Hi!
>
>> The whole point of releasing on Thursdays is so sysadmins have the
>> chance to update their servers in the event of known security problems
>> "before the weekend".
>> This point however becomes void when we release late Thursdays evening
>> American
62 Anatoliy Belsky
53 Stanislav Malyshev
46 Dmitry Stogov
45 Christopher Jones
36 Johannes Schlueter
32 Michael Wallner
29 Ilia Alshanetsky
28 Nikita Popov
17 Nuno Lopes
15 Derick Rethans
14 David Soria Parra
--
PHP Internals - PHP Runtime Devel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Please add all your questions here:
>
> https://wiki.php.net/vcs/gitfaq-usecases
>
> And let try to answer them one by one, for the best or recommended
> way to do something.
Thank you. makes sense to put it into the wiki and discuss it :).
First
It's PHP 5.4.1RC2 not RC1
On 2012-04-13, David Soria Parra wrote:
>
> Hello!
>
> Stas has packed PHP 5.4.1RC2 which you can find here:
>
> http://downloads.php.net/stas/
>
> The Windows team provides windows binaries which you find here:
>
> http://wi
Hello!
Stas has packed PHP 5.4.1RC2 which you can find here:
http://downloads.php.net/stas/
The Windows team provides windows binaries which you find here:
http://windows.php.net/qa/
Please ensure that the release is solid and all things behave
as expected! Please test this RC against
On 2012-04-01, Florian Anderiasch wrote:
> Hey there,
> due to the widespread acceptance of binary number format (0b1010101) and
> the growing demand for backwards compatibility I've started to work on
> support for Roman Numerals (I, II, III, ...)
>
> As you might know, this format cannot be stri
On 2012-03-31, Thomas Hruska wrote:
> I've been writing software for Windows in Visual Studio since forever
> and also know user-land PHP like the back of my hand and, even after a
> few Google searches, I'm still scratching my head over which PHP Windows
> binary download I want to use. If *I
On 2012-03-31, David Soria Parra wrote:
> Commit:3bf53aa911e1e2128a11aee45c126000635de006
> Author: David Soria Parra Sat, 31 Mar 2012 09:34:25
> +0200
> Parents: aa774a51d5c45b98103e0f67914d4c0b152e80ae
> ff8be9845f14a8156e7551033c2e98dad459f6fd
> Branche
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
alex fixed that
Am 30.03.12 15:08, schrieb Laruence:
> Hi: Today I make a fix which is only affect 5.3's test . after
> fix, I pushed it.
>
> then I do a fake merge(merge -s ours) in 5.4, then when I try to
> push it..
>
> I got an error:
>
> re
On 2012-03-24, Alexey Shein wrote:
> Hello,
>
> Just wanted to say that I updated multiple working dirs scenario here
> https://gist.github.com/2165086/, which is *much* more simplified now,
> thanks to dsp for hint about git-new-workdir script.
> It should work fine if all changes from downstream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Internals
we renamed the tags in the git repository to php-X.Y.Zdev. This avoids
an issue with current QA code. git pull origin --tags should give you
the new tags.
David
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Us
On 2012-03-22, David Soria Parra wrote:
> On 2012-03-22, Dmitry Stogov wrote:
>> Commit:14af1fe6923c65a91cd77eab5a8d4326f854391d
>> Author:Dmitry Stogov Thu, 22 Mar 2012 14:38:38
>> +0400
>> Parents: 523396cb28a0cb87ced9ec1179ef4f119d28ec80
&g
On 2012-03-22, Dmitry Stogov wrote:
> Commit:14af1fe6923c65a91cd77eab5a8d4326f854391d
> Author:Dmitry Stogov Thu, 22 Mar 2012 14:38:38
> +0400
> Parents: 523396cb28a0cb87ced9ec1179ef4f119d28ec80
> Branches: PHP-5.3 PHP-5.4
>
why are you commiting the patch 3 times? we have a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/21/2012 02:44 PM, Alexey Shein wrote:
> 21 марта 2012 г. 12:43 пользователь Sergey Ryazanov
> написал:
>> 21 марта 2012 г. 10:27 пользователь Alexey Shein
>> написал:
>>> 21 марта 2012 г. 3:34 пользователь Sergey Ryazanov
>>> написал:
H
On 2012-03-21, Ilia Alshanetsky wrote:
> Commit:9dcfb8c73fd639485182497ae5a8fc7d7ca7eb11
> Author:Ilia Alshanetsky Tue, 20 Mar 2012
> 21:07:08 -0400
> Parents: f3f76e5e8af265cd59d8edb7fb0827be6abc9a5a
> Branches: PHP-5.4
Please merge this into master in the future. I did the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/20/2012 09:48 PM, Ángel González wrote:
> El 19/03/12 21:29, David Soria Parra escribió:
>> On 2012-03-19, Kris Craig wrote:
>>> The workflow page currently recommends the "git:" one for
>>> cloning (which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/20/2012 06:29 PM, Kris Craig wrote:
> Quick clarification: On the other hand, by "pull request" are you
> simply referring to somebody else requesting that you "pull" their
> submission and merge/push it? If so, I get it, but I really think
> we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/20/2012 11:42 AM, Ferenc Kovacs wrote:
> I think it would be a good idea to explain why are we (not) doing
> that. AFAIR the reason is that if we hand out accounts on github,
> and somebody by mistake merges the pull request there (instead of
> p
Hi
with the php-src migrated to git we start receiving
pull request on github. A few things to notice:
- developers can pull the requests as described here:
https://wiki.php.net/vcs/gitfaq#github_pull_requests
- people with valid github accounts can comment
on pull request
- people
On 2012-03-19, Michael Wallner wrote:
> Shouldn't the commit mails reference the push mail?
> Looks a bit messy without relations of commit/push mails.
>
they should, it's just not working yet. I will look into it.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: h
On 2012-03-19, Kris Craig wrote:
> --f46d043892b5b345eb04bb9cfe02
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hey Chris,
>
> On Mon, Mar 19, 2012 at 11:40 AM, Christopher Jones <
> christopher.jo...@oracle.com> wrote:
> I sense your hostility but I think you misunderstood my question. The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>> [git] branch PHP-5.4 updated. | [git] commit ab33e5176ae
>> ext/lib/date
>
> Can we strip out as much "nonsense" from there as possible? I am
> mostly interested in the short part of the commit message; and not
> the words "commit", and the hash.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/19/2012 06:20 PM, Derick Rethans wrote:
> On Mon, 19 Mar 2012, David Soria Parra wrote:
>
>> There is also an FAQ at https://wiki.php.net/vcs/gitfaq.
>
> I can't find in the FAQ what's happening with the commit ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/19/2012 06:16 PM, Simon Schick wrote:
> 2012/3/19 David Soria Parra : Hi, David
>
> Thanks for this great step!
>
> As I quickly viewed into the github-repository I recognized the
> big list of branches ... 52 is quite a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/19/2012 06:18 PM, Stas Malyshev wrote:
> Hi!
>
>> The initial migration is done and initial testing was
>> successful.
>
> Thanks David! This is awesome! Great work and I think it will make
> developing PHP and contributing to the project much
Hi Internals,
The initial migration is done and initial testing was successful.
http://git.php.net/?p=php-src.git;a=summary
http://github.com/php/php-src
Please note that some branches and tags were renamed to make
the repository cleaner.
Please checkout the repository and play around. I ha
Migration is underway.
Will take a while. Import takes a few hours.
Expect git access to be available by Monday afternoon.
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/18/2012 07:31 PM, Derick Rethans wrote:
> David Soria Parra wrote:
>
>> we will start migrating the php-src repository today and SVN
>> access will be closed by 21:30 UTC.
> You'll leave it going read-only for a wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/18/2012 07:14 PM, Stefan Marr wrote:
> Hi David:
>
> On 18 Mar 2012, at 19:00, David Soria Parra wrote:
>
>> Hi Internals,
>>
>> we will start migrating the php-src repository today and SVN
>>
Hi Internals,
we will start migrating the php-src repository today and SVN
access will be closed by 21:30 UTC.
Thanks do Alexander Moskaliov we now have a much better, rewritten Mail script.
Thanks to Florian Anderiasch we have a bugweb script.
I added a wiki page for the workflow at http://wiki
On 2012-03-15, David Soria Parra wrote:
> Hi,
>
> I am sorry. I was ill in the last days and we some
> implementations were just finished. We have to
> delay the migration till Sunday 15. I am working
> workflow FAQ atm.
oh god, that's a mess. It's Sunday 18.
--
Hi,
I am sorry. I was ill in the last days and we some
implementations were just finished. We have to
delay the migration till Sunday 15. I am working
workflow FAQ atm.
David
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On 2012-03-10, Pierrick Charron wrote:
> --047d7b2ee19338d79004bae668f3
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi all,
>
> As you may know, the cURL PHP extension is currently not in sync
> (featurewise) with the original libcurl. I started to work on it to
> make it as close as possib
On 2012-03-07, Kris Craig wrote:
> --f46d044304ec4e135704baa12342
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Tue, Mar 6, 2012 at 10:09 PM, Kiall Mac Innes wrote:
>
>> On Wed, Mar 7, 2012 at 6:03 AM, Drak wrote:
>>
> I know I keep promising to draft an RFC for this lol, so I'll make it
On 2012-03-05, Matthew Weier O'Phinney wrote:
> On 2012-03-02, David Soria Parra wrote:
>> just a heads up. The PHP_5_4 branch is open for commits again.
>
> Related: With 5.4.0 out... how soon will the cutover to git occur?
March 15.
--
PHP Internals - PHP Runtime Develop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/04/2012 10:32 AM, Jaroslav Hanslik wrote:
>>
>> (3) Karma system fixes. Already done by me. People who have
>> access to the root of a repository are able to do forced pushes.
>>
>
>
> Do you think it's good idea not to forbid forced pushes a
1 - 100 of 230 matches
Mail list logo
