Daniel Stenberg wrote:
>> Seriously - how about not being so f-ing eager to add anything and
>> everything new just because it exists WHEN YOU HAVE BEEN TOLD THAT THERE
>> IS MORE TO THE STORY?
> You disappear and you expect the world to pause waiting for your return?
I expect you and Marc to communicate with me before taking further
action when you know that there's a reason to do so, even if I seem
to have disappeared. Quite likely I haven't disappeared very far.
> the world doesn't wait and hold off their work just because single
> contributors drop off or need more time for something.
That's exactly the problem I'm talking about. When "the world"
doesn't communicate, neither in advance nor after the fact, then
the end result is a lot worse than would be neccessary.
> I push a patch in *SEPTEMBER* that was posted here in *MAY* and you think
> I'm "f-ing eager" because of that? Clearly we're not living under the same
> rock. I would call that "dead slow".
You push a patch the day after (or was it same day?) Marc reminded
you about it, without even trying to get in touch with me, even
though Marc indicated that I had something to add to the subject.
Marc's wording misrepresented me by mistake, but even so it was clear
that I had some connection to this patch.
Knowing that and pushing Marc's patch without seeking my comment,
or even just waiting more than hours for me comment on my own (though
I've been offline on vacation for the last few weeks) is the problem,
and what I call "f-ing eager".
> And why does me pushing the original patch cause a problem to your
> work on top of that in the first place?
This is completely unrelated to the problem but as I explained when
Marc first posted the patch my commits are infrastructure changes
which simplify supporting different crypto providers. I think it's
pretty obvious which order makes more sense.
> show us the code
If you had even pretended to care about communicating with me then I
would have been quite eager to finish my commits to get them and
Marc's change into the next release.
Now, not so much.
Received on 2013-09-10