On Mon, 25 Jan 2016, Volker Braun wrote:
Examples of not "getting" code review from this thread:
* At review of some small addition we start a general discussions about what
Poset should do and then everybody votes on thatÂ
* Dislike of change/design pattern/author/..., hence I'm not reviewing t
> That thinking is precisely whats wrong here, there is no dead end. If you
> dislike how Poset is being used then change it or get over it. But sulking
> in your corner with this never-compromising obstructionist attitude is
not a
> way forward.
"Sulking in my corner with this never-compromising
On Monday, January 25, 2016 at 11:28:21 AM UTC-5, Nathann Cohen wrote:
>
> And really, I don't think that we could devise a new set of rule that
> could solve this kind of dead-end situations.
That thinking is precisely whats wrong here, there is no dead end. If you
dislike how Poset is being
On Mon, Jan 25, 2016 at 8:28 AM, Nathann Cohen wrote:
>> Examples of not "getting" code review from this thread:
>> * At review of some small addition we start a general discussions about what
>> Poset should do and then everybody votes on that
>> * Dislike of change/design pattern/author/..., hen
> Examples of not "getting" code review from this thread:
> * At review of some small addition we start a general discussions about what
> Poset should do and then everybody votes on that
> * Dislike of change/design pattern/author/..., hence I'm not reviewing this
> * I just make some comments on
> Examples of not "getting" code review from this thread:
> * At review of some small addition we start a general discussions about what
> Poset should do and then everybody votes on that
> * Dislike of change/design pattern/author/..., hence I'm not reviewing this
> * I just make some comments on
