Bug#736523: Indeed, python-concurrent.futures is the same
> This kind of message saddens me.
the same holds for calling my packages as having "lots of problems"
(none of them ever being reported as bugs by any of the current users,
nor even by you) of accusing me of having done something without
thinking.
> I'm not expecting this kind of
> interaction, but rather:
>
> "thanks for fixing that, however there, you shouldn't have done this,
> plus let me revert and fix that bit better"
and so I was expecting you to contact me *upfront* almost redoing the
packaging, and switching helper, but it did't come, did it?
> Maybe you could try this style and really do team work if your package
> is team maintained, no?
"really do team work"? do you call your changes a "team work"? i
don't. teams talk, teams discuss, teams agree on a solution - you just
uploaded a package that fixes your problem without caring to
understand if that's ok with who maintainer (that far).
it is not the first time your interactions with DMPT or its team
members has been problematic (if you need a hint, think about all the
problems your fanatism to GIT has generated): maybe it's you that
should rethink how you interact with the team and stop imposing your
way.
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
Reply to: