-1
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hannes Magnusson wrote:
On Sun, May 18, 2008 at 8:14 PM, David Soria Parra [EMAIL PROTECTED] wrote:
Hannes Magnusson wrote:
On Sun, May 18, 2008 at 7:15 PM, David Soria Parra [EMAIL PROTECTED]
wrote:
dsp Sun May 18 17:15:08 2008 UTC
Modified files:
/php-src/ext/mcrypt
Everyone is welcomed to participate in the mysqlnd development and the
extension has seen changes from outside, as well the mysql extensions
and we never complained that someone does it. I just moved the changes
to our internal revision control system, as Bazaar gives us more freedom
to work
However I think we should provide the infrastructure for developers to
setup a dvcs. I dont know if we want to standardize on a specific one.
But collaboration on exterimental stuff that requires a dvcs should be
possible on php.net servers.
Maybe it's just about having the possibilities for
-dnl Only allow AC_PROG_CXX if it's explicitly called (by PHP_REQUIRE_CXX)
-dnl otherwise AC_PROG_LIBTOOL fails if there is no working C++ compiler
-AC_PROVIDE_IFELSE([PHP_REQUIRE_CXX], [AC_PROG_CXX], [undefine([AC_PROG_CXX])
-AC_DEFUN([AC_PROG_CXX], [])])
+dnl Only allow AC_PROG_CXX and
Andrei Zmievski wrote:
Whatever happened to the Subversion migration effort?
-Andrei
As far as I know the actual conversion is done, but a lot of the
CVSROOT/ scripts are not yet rewritten to fit the subversion hook
system. Also Marcus proposed and I guess it was somehow accepted, that
the
I recently noticed if you want to compile PHP using the suncc compiler,
there are no useful default flags set by configure. Therefore if there
are no objections I want to commit the following patch that introduces
usefull cflags (actually those used by php distributed by sun) for the
suncc
1) ext/mhash in 5.3. ext/hash has all the functions, so the entire BC
break will be that if (extension_loaded('mhash')) will need fixing if
mhash is removed (answer both)
I) enable ext/hash by default
II) remove ext/mhash
+1 +1
2) deprecate ereg*. ext/ereg is an extension as of PHP 5.3. Since
Hi Internals,
as I recently worked with different compilers, and I noticed that we
always check for gcc by default. This means even your /usr/bin/cc is
_not_ gcc, PHP's buildsystem will use gcc if it's found. This is the
default behavior of the AC_PROG_CC macro.
In my opinion, I think if people
Hi List,
I recently discovered that zend_hash_func is equal to
zend_get_hash_value. To clean this up, I would like to remove
zend_hash_func in favor of zend_get_hash in HEAD. If there are no
objections I would commit a patch in a few days.
David
--
PHP Internals - PHP Runtime Development
On 2009-06-23, David Soria Parra d...@php.net wrote:
dsp Tue Jun 23 14:15:28 2009 UTC
Modified files: (Branch: PHP_5_3)
/php-src/ext/mysqlnd mysqlnd_result.c
Log:
MFH: Fix bug #48644 mysqlnd does not compile with
'--enable-mysqlnd-threading
On 2009-07-07, Thomas Koch tho...@koch.ro wrote:
Hi,
are there people who're interested to host semi-official
GIT-/HG-/BZR-mirrors?
Doing an initial GIT-SVN sync causes quite a lot of traffic on the subversion
server and if a douzens people set up there mirrors in the next week, this
-1 for 5.3.x . We should not add major language features at that stage.
On 2009-07-07, Ilia Alshanetsky i...@prohost.org wrote:
Last week or so there was a fairly detailed discussion on the
internals list regarding type hinting based on my original patch.
Since then the patch has been
Hi List,
Quite a few people mentioned that they want to use git as a frontend to
the svn server. Therefore most of them need an initial import of the
svn.php.net repository using git-svn. As this operation will retrieve
every version in the repository, we decided to offer a semi-official git
On 2009-07-13, sean finney sean...@debian.org wrote:
--rwEMma7ioTxnRzrJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
hi david,
On Mon, Jul 13, 2009 at 03:38:04PM -0400, David Soria Parra wrote:
svn.php.net repository
Hi List,
in the last months I worked on adding DTrace probes to PHP and would
like to start a discussion about the RFC and patch against trunk
that can be found at:
http://wiki.php.net/rfc/dtrace
DTrace is a dynamic tracing framework for Solaris, OpenSolaris, Mac OSX
and FreeBSD that can be
On 2009-07-15, Alexey Zakhlestin indey...@gmail.com wrote:
The patch is simple and clean. Just 2 notices..
1) Zend/zend_dtrace.h file is generated. Are you sure it should be the
part of patch?
The generated dtrace header on Solaris and MacOS are different.
Therefore people have to generate
On 2009-07-15, Alexey Zakhlestin indey...@gmail.com wrote:
The problem is, that if we update Zend/zend_dtrace.d, this header file
will need to be regenerated.
So, there is a need for a corresponding procedure.
I'll change the patch as soon as possible to generate the header file
during
On 2009-07-16, Andrey Hristov p...@hristov.com wrote:
Hi,
does it makes sense? Once we renamed php-dev to internals, so this won't
be the first ML rename.
if we really need that we better use php-commits or something similar.
--
PHP Internals - PHP Runtime Development Mailing List
To
On 2009-07-14, David Soria Parra david.soriapa...@sun.com wrote:
Hi List,
in the last months I worked on adding DTrace probes to PHP and would
like to start a discussion about the RFC and patch against trunk
that can be found at:
http://wiki.php.net/rfc/dtrace
If there are no other
On 2009-07-16, Pierre Joye pierre@gmail.com wrote:
I doubt any tools can really help to automatically help to merge
changes from one branch to another (in php). However there are many
very good merging tools (with UI) out there to ease this process
(meld, winmerge, etc.).
In that case
On 2009-07-19, Christopher Jones s...@php.net wrote:
--0c1c83a6b4cbab36310748c87058a6f52e7ad90a
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
sixd Sun, 19 Jul 2009 16:27:59 +
URL: http://svn.php.net/viewvc?view=revisionrevision=284377
On 2009-07-27, Takeshi Abe t...@php.net wrote:
Log:
MFH: fixed #48732 (TTF Bounding box wrong for letters below baseline) and
#48801 (Problem with imagettfbbox)
please commit the changes to 5.3/5.2 and trunk at once in one changeset
instead of MFH'ing. Thanks
--
PHP Internals - PHP Runtime
As Lukas pointed out, both approaches have flaws, but I think
the new merging approach is much cleaner and prevents people
from committing during a freeze.
Although the wiki might not be the perfect place to do things,
I think the general approach is good. Core developers should
know what's
Hi Internals,
I noticed that getopt() is not available on windows machines. Therefore I
tried to look for a solution. I build a patch, which does nothing
else than using the getop.c from the FreeBSD libc. This should be license
compatible (3-clause BSD License) as some other sources from the
Hi internals,
so based on a discussion of php.pecl we thought about using the php_getopt
for the PHP_FUNCTION(getopt) instead of the system provided getopt. Here
is the patch for that. Hopefully someone is reviewing and commiting the
patch as i don't have karma.
It addes main/getopt.c
Why one would need getopt outside of cgi/cli? I.e. where would these
options come from?
initially the idea was to use getopt on windows machines. After proposing
my patch which just includes the NetBSD getopt(), there was a
recommandation in php.pecl to use the php_getopt instead of the system
Hi internals,
once again a proposal for a bugfix.
This time concerning http://bugs.php.net/bug.php?id=40501.
As the standard escape character is \\ , but the RFC says , I added a
optional escape character to the function call as a last parameter.
Furthermore, when the escape character is the
Hi internals,
another small patch. This time concerning
http://bugs.php.net/bug.php?id=42818. As I'm not a ZendEngine expert I'm
not sure if this is the right place and the right way to fix the bug, but
at least for me this small fix works fine. Maybe somebody who is really
into depth with the
Hi internals,
I was asked by Jani to apply for extending my karma rights from my PEAR
right to php-src. (As the form on the website ist just for new users and i
allready have a cvs account with username dsp i do it that way)
greets
David
--
PHP Internals - PHP Runtime Development Mailing List
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:
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
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
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
On 2012-09-08, David Soria Parra d...@php.net 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
dedicate
On 2012-09-17, Sebastian Bergmann sebast...@php.net 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
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
Ramadan theanomaly...@gmail.comwrote:
On Fri, Nov 2, 2012 at 11:21 AM, David Soria Parra d...@php.net 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 to next Tuesday.
So 5.4.9RC1 will be tagged
On 2012-11-13, Adam Harvey ahar...@php.net wrote:
On 13 November 2012 01:16, Ferenc Kovacs tyr...@gmail.com wrote:
On Mon, Nov 12, 2012 at 4:00 PM, Ulf Wendel ulf.wen...@oracle.com wrote:
Don't bother. There is a standard way of deprecation, at least I assume
there is. Its proven. Use it: docs
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 for
-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 d...@php.net wrote:
Following the versioning
On 2012-11-15, d...@php.net 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
On 2012-12-06, Sebastian Bergmann sebast...@php.net 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:
On 2012-12-05, Sara Golemon poll...@php.net 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
-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 2013-01-09, Rasmus Lerdorf ras...@lerdorf.com 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).
On 2013-01-18, Stanislav Malyshev s...@php.net wrote:
Commit:33b104c778c5c0e5446671397aaddd66efa4a7bc
Author:Stanislav Malyshev s...@php.net Mon, 14 Jan 2013
00:06:09 -0800
Parents: f63a9f6c11c05aa76158b6cae0e05340d303a6af
Branches: PHP-5.3 PHP-5.4 PHP-5.5 master
Link:
On 2013-01-19, Xinchen Hui larue...@php.net wrote:
Commit:f7b99c481d0a943d922e99ad9afa82c45193030e
Author:Xinchen Hui larue...@php.net Sat, 19 Jan 2013 17:01:57
+0800
Parents: e23fca8910b96f1c3bb26c6582c17c92fd6f2f7a
Branches: PHP-5.5
Link:
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
On 2013-01-28, Zeev Suraski z...@zend.com 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
On 2013-01-29, Zeev Suraski z...@zend.com 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
-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
On 2013-02-19, Stas Malyshev smalys...@sugarcrm.com 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
On 2013-02-21, Rasmus Lerdorf ras...@lerdorf.com 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
On 2013-02-27, Zeev Suraski z...@zend.com wrote:
On 27 2013, at 18:58, Anthony Ferrara ircmax...@gmail.com 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
On 2013-03-07, Rasmus Lerdorf ras...@lerdorf.com 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
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
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 nitpick
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 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!
RFC that are
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/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
pro:
-
On 2013-03-26, Ond?ej Sur? ond...@sury.org 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
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-04-12, Johannes Schl�ter johan...@schlueters.de 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
On 2013-04-17, Pierrick Charron pierr...@adoy.net 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
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 poll...@php.net
Date: Mon Apr 22 14:57:05 2013
On 2013-04-25, Stas Malyshev smalys...@sugarcrm.com 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
On 2013-05-17, Remi Collet r...@fedoraproject.org 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
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,
On 2013-06-19, Johannes Schl�ter johan...@php.net 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
On 2013-06-19, Johannes Schl�ter johan...@php.net 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
On 2013-06-25, Ferenc Kovacs tyr...@gmail.com 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
On 2013-08-27, Lior Kaplan lio...@zend.com 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
On 2011-07-27, Pierre Joye pierre@gmail.com wrote:
hi Gustavo,
Could you apply your patch tomorrow please? So we have it for the
alpha3 on Thursday.
Hi Pierre,
I think you confuse dates here. Alpha 3 is planned for August 4. So it's
tomorrow
in a week.
Thanks anyawy for moving forward
Hello!
Stas has packed PHP 5.4.0alpha3 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 test it carefully, and report any bugs in the bug system, but
only if you have a short
Hi Internals,
Distributed Version Control Systems (DVCS) getting more and more
popular. In fact they have been discussed within the PHP community and
on Internals a few times. It came to my attention that more and more
people like to see PHP move to a DVCS to solve some of the current
issues (and
On 2011-08-07, Richard Quadling rquadl...@gmail.com wrote:
I feel I have a major objection to using a DVCS for PHP.
Currently, a single source provides a sense of authority. If bad code
is committed, it will be quickly dealt with. If good code is
incomplete it may be withdrawn or fixed. In
On 2011-08-07, Stas Malyshev smalys...@sugarcrm.com wrote:
Hi!
As somebody that have seen reasonably big project switch from SVN to git
and worked quite actively with git since then, I think describing my
experience might be useful for those that never tried it.
1. git is much better than
On 2011-08-07, David Soria Parra d...@php.net wrote:
Hi Internals,
Distributed Version Control Systems (DVCS) getting more and more
popular. In fact they have been discussed within the PHP community and
on Internals a few times. It came to my attention that more and more
people like to see
On 2011-08-18, Lester Caine les...@lsces.co.uk wrote:
Again neither of those seem to be using 'superprojects', just the odd library
included as a submodule.
It seems that the statements in the RFC were not clear enough, I'll add some
explanation.
We will very probably not use submodules in
Hi Internals,,
after 3 weeks of discussion, I think we are ready to start voting on
the DVCS RFC. If you think something is missing or should be explained
in more detail, let me know.
Votes can be found here:
https://wiki.php.net/rfc/dvcs/vote
The RFC can be found here:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/24/2011 11:15 PM, Stas Malyshev wrote:
Hi!
On 8/24/11 2:03 PM, David Soria Parra wrote:
Hi Internals,,
after 3 weeks of discussion, I think we are ready to start voting
on the DVCS RFC. If you think something is missing or should
On 2011-08-24, Ferenc Kovacs tyr...@gmail.com wrote:
On Wed, Aug 24, 2011 at 11:15 PM, Stas Malyshev smalys...@sugarcrm.com
wrote:
Hi!
On 8/24/11 2:03 PM, David Soria Parra wrote:
Hi Internals,,
after 3 weeks of discussion, I think we are ready to start voting on
the DVCS RFC. ??If you
On 2011-08-24, Lester Caine les...@lsces.co.uk wrote:
David Soria Parra wrote:
I'm not sure choosing DCVS by vote is actually a good way to go here.
I think we need much more input from people that maintain all the
infrastructure we're using now and would be doing the move. If we
don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/25/2011 11:28 AM, Ivan Enderlin @ Hoa wrote:
On 25/08/11 11:15, Derick Rethans wrote:
On Wed, 24 Aug 2011, Stas Malyshev wrote: I agree, and I also think
that before people can make a choice they need to have played with
all the options.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/25/2011 11:56 AM, Ivan Enderlin @ Hoa wrote:
On 25/08/11 11:37, David Soria Parra wrote:
On 08/25/2011 11:28 AM, Ivan Enderlin @ Hoa wrote:
On 25/08/11 11:15, Derick Rethans wrote:
On Wed, 24 Aug 2011, Stas Malyshev wrote: I agree, and I
Hi Internals,
after 2 weeks of voting and discussion, I closed the votes today. The results
are fairly straightforward. Most of the users want to move to a decentralized
version
control system.
52 want to switch to git
15 want to switch to Mercurial
1 for bazaar
13 want to stay
Hello!
Stas has packed PHP 5.4.0beta1 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 test it carefully, and report any bugs in the bug system, but
only if you have a short
On 2011-09-16, David Soria Parra d...@php.net wrote:
Hello!
Stas has packed PHP 5.4.0beta1 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 test it carefully, and report any
On 2011-09-26, Stas Malyshev smalys...@sugarcrm.com wrote:
Hi!
On 9/26/11 1:42 AM, Pierre Joye wrote:
It may be good to merge
http://svn.php.net/viewvc?view=revisionrevision=311748 to 5.4 too.
This commit is about issues similar to the one describe in #54918.
Any reason not to do it before
On 2011-10-16, Stas Malyshev smalys...@sugarcrm.com wrote:
Hi!
On 10/7/11 2:11 AM, Michael Wallner wrote:
So I can only see two solutions:
- either disallow serialize/unserialize in __sleep/__wakeup
- or revert r299770
So, what is the status of this? I think we better revert it for 5.4
On 2011-10-24, Stas Malyshev smalys...@sugarcrm.com wrote:
Hi!
ESR proposes his help to OSS projects in converting SVN projects to Git:
http://esr.ibiblio.org/?p=3839
Just thought it might be interesting.
I'll take a look. at the moment I'll plan to start working on the transition
proposal
Hello!
Stas has packed PHP 5.4.0RC1 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/
This is the first release candiate. No new features will be included
before the final version of PHP
On 2011-11-12, David Z?lke david.zue...@bitextender.com wrote:
Had a few other tests failing, updated those accordingly and attached a newer
version.
According to the RFC it should not throw an error, so I think your patch is
fine.
If Pierre, who implemented it, doesnt have an objection I'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I committed zuelke's patch.
On 11/15/2011 02:23 PM, Pierrick Charron wrote:
I also worked on the patch and I agree this is just an error :) I
can do the change if you want.
Pierrick
On 15 November 2011 07:51, David Soria Parra d...@php.net
On 2011-11-21, Gustavo Lopes glo...@nebm.ist.utl.pt wrote:
-static void php_intl_idn_to(INTERNAL_FUNCTION_PARAMETERS, int mode)
+/* like INTL_CHECK_STATUS, but as a function and varying the name of the
func */
+static int php_intl_idn_check_status(UErrorCode err, const char *msg, int
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/21/2011 01:23 PM, Pierre Joye wrote:
hi,
After a short talk on IRC, we agreed to go with the solution 1.
David, Stas, any objection for 5.4? As it adds a new feature it is
actually a bug fix too.
- From my side it's okay to add it.
Hello,
The PHP team released the second release candidates of PHP 5.3.9 and PHP
5.4.0 today:
You can find the packages for PHP 5.3.9RC2 here:
http://downloads.php.net/johannes
and respectively for PHP 5.4.0RC2:
http://downloads.php.net/stas
The Windows team provides windows binaries
Hello Internals,
We followed our 14 days cycle for release candidates, so today is
release day.
The PHP team announces the availability of the third release candidates
of PHP 5.3.9 and PHP 5.4.0 today:
You can find the packages for PHP 5.3.9RC3 here:
http://downloads.php.net/johannes
and
1 - 100 of 223 matches
Mail list logo
