On Sat, Jun 14, 2014 at 10:52 AM, Pierre Joye <[email protected]> wrote:
> On Sat, Jun 14, 2014 at 7:35 PM, Hannes Magnusson
> <[email protected]> wrote:
>
>> Please do. Anatol recently pushed ~50 commits to that repo that had
>> been live for a long time, so it does not look like it. I have asked
>> this question frequently in this thread. Your latest answer was "stop
>> spreading FUD"?!?
>
> About your corporate BS as usual. Get over it, it only adds noises to
> your signal.
>
>
>> If you stop being excessively passive aggressive and stop derailing
>> every discussion and simply answer the question we would get much
>> better along - and safe sooooo much time.
>
> I told you what is being done, what is the plan, what we are working
> on, my team and other, which has been involved in these tasks, for
> very long. You have a sudden need/interest to give snapshot a boost?
> Very good, come over and contribute to the right place.

Where is that place?
Let me repeat, in case your english is just that bad: I would like to
develop snapshot capabilities into the Windows PECL build
infrastructure.
It was your people that told me this should be implemented into
rmtools, look a the early start of this thread before you started
making stuff up.
I don't care which tool I need to work on to get it done. If its
better to build it into some other tools then please tell me. I cannot
read your mind.


> However, insisting/harrasing us about the wrong tool for the right

It was Anatol:
"rmtools can be adapted which would spare time. That's effectively a"

if that is not correct, it is not my fault and you need to apologize
for how you have been acting in this conversation.

I don't care what tool I need to modify to get this implemented. I
have no existing stake in the matter and honestly don't care for any
political powers that may or may not be involved.


I repeat again for your pleasure: I would like to contribute this
functionality. Which project do you want it in? And where is the
current canonical source for it?



> task is not going to bring us anywhere but in yet another painful
> discussion.

I don't know what is up your ass, but until you joined this thread it
was going just fine.
It is your endless twisting people words, lies, pretending to do
something and destructive attitude that kills any attempt by
volunteers to join the project - and current contributors to steer
away.




>>> But again, do PRs pls. This code is used for the core as well and RMs
>>> relies on it to valid releases etc.
>>
>> I've no interest in touching that code. All I am trying to work on is
>> creating a pecl build on-demand to verify it builds before actually
>> rolling out a release. Upon succeeding doing that, the ideas Anatol
>> and I came up with earlier in this thread will be worked on.
>
> As I told you many times already, this not what will be used for
> snapshots, on demand or not.
>
> Our team (which Anatol is part of) has worked on rmtools to ease our
> work with pecl's extension, as a temporary solution. The plan remains
> what i have described in your very first post.


Then if he is misunderstanding something and this shouldn't be
implemented into rmtools, then I ask again: Where should it be
implemented?
Please answer with a link to the repository (and branch if relevant)
to safe us from needing to talk more to eachother.


>>> And *again*, this is not what we will use for pecl snapshots, not for
>>> the build part. So can you please understand that and stop pushing
>>> that all of a sudden while we are working on the final solution?
>>
>> Great. So where can I implement this functionality? What will be used?
>> For the past now 3weeks we have been discussing this subject and not
>> until you decide to derail the discussion has it ever been brought up
>> before that anything else will be used.
>> So please understand that you need to be transparent, even within your
>> own team, since they clearly have no idea.
>
> They clearly have a good idea, and I can discuss that daily, be on the
> lists or directly. But you insist on using something that won't be
> used for pecl builds. Understand that.


I have not insisted on anything other then finding out where the
system is, how I can replicate it so I can develop new functionality
for it.

The only thing I am insisting on is to get answers.


-Hannes

-- 
PECL development discussion Mailing List (http://pecl.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to