Yes, IF you're using a proper branching model. If you're just using it the
same way you'd use Subversion, which currently is the direction we seem to
be moving in, those advantages are mostly negated.
I agree that PHP 5.5 (and maybe even 5.6, etc) should come before PHP 6.
That being said, at som
On Fri, March 2, 2012 4:26 am, Ferenc Kovacs wrote:
> If we can agree upon the next version number beforehand, and we decide
> that
> we will go with the major release (be that php 6 or 7, whatever), we
> don't
> to do anything right now, we can branch the version from trunk/master,
> when
> the ti
2012.03.13 16:38 Richard Lynch rašė:
> I'd have to agree with Stas that everybody should start passing in a
> variable there, that can be set somewhere in a config, or, perhaps,
> would DEFAULT to, e...
You do realize that suggestions on this thread and original bug reporter
failed to make cor
+1
Git can be confusing for seasoned Subversion developers at first, as it
really is a fundamental paradigm shift in many respects. I'm not sure why
you're only able to do read-only access, though. The add/commit syntax for
Git is fairly similar to that of SVN. Have you tried creating a dummy r
On Wed, March 7, 2012 1:51 pm, Sebastian Bergmann wrote:
> Am 07.03.2012 19:46, schrieb Kris Craig:
>> As I and others have said already, using a Subversion branching
>> model
>> on Git just doesn't make any sense.
>
> How often does it have to be explained to you and others that we
> would
> lik
On Mon, March 12, 2012 2:44 pm, Rasmus Lerdorf wrote:
> But you can't necessarily hardcode the encoding if you are writing
> portable code. That's a bit like hardcoding a timezone. In order to
> write portable code you need to give people the ability to localize
> it.
If you wanted it portable, wo
Am 13.03.2012, 02:34 Uhr, schrieb Rasmus Lerdorf :
On 03/12/2012 05:52 PM, Yasuo Ohgaki wrote:
I always set all parameters for htmlentities/htmlspecialchars, therefore
I haven't noticed this was changed from 5.3. They may be migrating from
5.2 or older. (RHEL5 uses 5.1)
No, like I showed, movi
We could add a flag to disable the @ usage but I'm against having the
'@' usage disabled by default. This BC break would be in my opinion
too big.
An other solution would be to have something like (We will also have
to add the type and filename support to this solution so this is just
a first prop
On Mon, Mar 12, 2012 at 23:11, Christopher Jones
wrote:
> The autom4te.cache and *.orig files originally mentioned are included in
> php.net's php-5.4.0.tar.bz2
> I.e. this is a valid issue.
>
> Ondřej, please log a bug.
https://bugs.php.net/bug.php?id=61368
O.
--
Ondřej Surý
--
PHP Internal
