Hi
I was looking into CR:
48774(http://bugs.php.net/bug.php?id=48774&thanks=3) and was hoping if
some one can kindly review this patch. This patch does address the SEGV
issue reported in the bug. Can this be applied to PHP 5.3 and PHP 5.2 as
well ?
Index: ext/curl/interface.c
=
On 18.07.2009, at 01:01, Matteo Beccati wrote:
Greg Beaver ha scritto:
Matteo Beccati wrote:
Not really: it will copy the link, not its content. At least that
was my
experience when I managing releases for an internal project using
externals. What I usually did was to change the externals p
Greg Beaver ha scritto:
> Matteo Beccati wrote:
>> Not really: it will copy the link, not its content. At least that was my
>> experience when I managing releases for an internal project using
>> externals. What I usually did was to change the externals property to
>> point to a specific revision,
Matteo Beccati wrote:
> Lukas Kahwe Smith wrote:
>
>> On 17.07.2009, at 03:04, Johannes Schlüter wrote:
>>
>>
>>> On Thu, 2009-07-16 at 18:20 -0500, Greg Beaver wrote:
>>>
I'd like to consider instead using svn:externals to pull in PEAR stuff
directly from a STABLE branch f
Lukas Kahwe Smith wrote:
>
> On 17.07.2009, at 03:04, Johannes Schlüter wrote:
>
>> On Thu, 2009-07-16 at 18:20 -0500, Greg Beaver wrote:
>>> I'd like to consider instead using svn:externals to pull in PEAR stuff
>>> directly from a STABLE branch from somewhere in the pear/ hierarchy.
>>> This wo
Davey Shafik wrote:
More importantly, the branch/merge support in SVN is limited to
temporary feature/bug branches. You branch, *complete* the feature/bug
fix, and then merge it in. After that, if you decide to carry on in your
branch, SVN's merge tracking cannot handle the tracking of changes.
On 17/07/09 12:24 PM, Lukas Kahwe Smith wrote:
...
also using merge tracking is only fun if everybody does it .. because if
only some people use it .. they first have to figure out which things
have not been merged via svn merge, as svn merge updates its metadata.
when merging you can either mark
On 17.07.2009, at 19:40, Jeff Griffiths wrote:
On 17/07/09 8:31 AM, Davey Shafik wrote:
...
More importantly, the branch/merge support in SVN is limited to
temporary feature/bug branches. You branch, *complete* the feature/
bug
fix, and then merge it in. After that, if you decide to carry on
On 17.07.2009, at 03:04, Johannes Schlüter wrote:
On Thu, 2009-07-16 at 18:20 -0500, Greg Beaver wrote:
I'd like to consider instead using svn:externals to pull in PEAR
stuff
directly from a STABLE branch from somewhere in the pear/ hierarchy.
This would allow us over at PEAR to push the ins
On 17/07/09 8:31 AM, Davey Shafik wrote:
...
More importantly, the branch/merge support in SVN is limited to
temporary feature/bug branches. You branch, *complete* the feature/bug
fix, and then merge it in. After that, if you decide to carry on in your
branch, SVN's merge tracking cannot handle t
On Jul 16, 2009, at 08:01 PM, shire wrote:
Pierre Joye wrote:
On Fri, Jul 17, 2009 at 12:45 AM, shire wrote:
Jani Taskinen wrote:
Rasmus Lerdorf wrote:
One of the benefits of svn is that we can do cross-branch commit
pretty
easily now and thus avoid multiple similar commits with annoying
On Fri, Jul 17, 2009 at 11:21, Keryx Web wrote:
> Please forgive me bumping this, bit I think my questions are valid and I
> can't find authoritative and relevant info on php.net or Google.
The future has yet to be written. All we can do is to predict.
The current prediction is that ctype will use
On 07/17/2009 01:24 AM, Jani Taskinen wrote:
Rasmus Lerdorf wrote:
One of the benefits of svn is that we can do cross-branch commit pretty
easily now and thus avoid multiple similar commits with annoying MFH/MFB
commit log messages that are hard to track.
I did a commit today on all 3 branches
Please forgive me bumping this, bit I think my questions are valid and I
can't find authoritative and relevant info on php.net or Google.
If indeed I have broken protocol, as feared in my ending, could anyone
please tell me so (off list in order to reduce the noise, of course) and
kindly point
14 matches
Mail list logo