Felipe Contreras wrote:
> On Thu, May 30, 2013 at 12:23 AM, Jonathan Nieder <jrnie...@gmail.com> wrote:
>> Felipe Contreras wrote:
>>> On Wed, May 29, 2013 at 6:43 PM, Jonathan Nieder <jrnie...@gmail.com> wrote:
>>>> A bigger problem (in my opinion) with allowing arbitrary changes to
>>>> the meaning of existing commands is that scripts, whether placed in
>>>> .sh files or given as commands to run over IRC, stop working
>>>> altogether. It's nice to have commands like "git log" and "git am"
>>>> mean the same thing no matter what machine I am on.
>>> Except that's not true:
>> It's not true that my opinion is that a bigger problem than the
>> non-problem Ram mentioned with allowing arbitrary changes to the
>> meaning of existing commands is that scripts stop working reliably?
> It's not true what you said:
> commands like "git log" and "git am" mean the same thing no matter
> what machine I am on.
It's not true that it's nice when they do?
>> This combative style of communication is toxic. It kills the chance
>> of a calm, pleasant discussion, even with patient people who don't
>> even fundamentally disagree. Please stop it.
> Stop assuming bad faith.
Perhaps you mean "I'm trying, but I'm human --- please bear with me
while I work on improving. Know that my intentions are good."
Unfortunately, good intentions are not enough. Communicating in a way
that clearly conveys what you mean instead of something else that
derails the conversation is a real skill and, as I said, it's an
important one that is basic to being able to have a productive
conversation. If you are working on it and are not there yet, my best
advice would be to lurk more and speak less, to learn from the example
of others, and to start by working on how to receive criticism and to
clear up misunderstandings, which can at least mitigate the damage
when things go wrong.
You have accused others of assuming bad faith in the past, which only
escalates things. It's not a good way to move forward. It's possible
that the best way to move forward involves some way (e.g., mail client
configuration that holds messages in "drafts" for a little while
before sending them out) of being able to cool down when discussions
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html