Felipe Contreras <felipe.contreras@xxxxxxxxx> writes: > Michael Haggerty wrote: >> On 05/12/2014 12:37 PM, Felipe Contreras wrote: >> > Michael Haggerty wrote: >> >> On 05/12/2014 01:34 AM, Felipe Contreras wrote: >> >>> Recently Junio said he was willing to hear the opinion of other people >> >>> regarding the move from contrib to the core[1]. This move is already >> >>> under way, but suddenly Junio changed his mind. >> >> >> >> I agree with Junio. There are good technical arguments for and against >> >> moving git-remote-hg out of contrib. >> > >> > Saying you agree with Junio is content-free. You have to say *why* you >> > agree. >> >> Actually, I don't have to, > > Then there's no point in reading what else you have to say. Whatever > reasons you might have to agree with Junio are known only to you, thus > your "agreement" is opaque and meaningless. Let me spell it out for you. Michael states "I agree with Junio. There are good technical arguments for and against moving git-remote-hg out of contrib." Since there are arguments for both sides, the decision boils down to a judgment call. Michael states that he condones the choice Junio made, based on the reasoning he gave. Does that mean that he examined the choice with equal detail and remembers every detail? No. In such a decision, both technical expertise as well as trust based on a past record factor in. >> > The quality of the subjproject has not been called into question, >> > stop taiting the discussion with red herrings. >> >> On the contrary. I just called the quality of the subproject into >> question, and I stated exactly which aspects of its quality I find to >> be inadequate in the text that you omitted from your response: > > I'll wait until somebody else calls into question the quality. > Preferably somebody who backs up his claims with evidence. The evidence for the toxicity of dealing with subprojects maintained by you is all over the mailing list. You are obviously blind to it yourself. Feel free to print out a few salient threads where you argue in favor of your points and ask someone you trust about his impression about how you come across. >> > Let's see how sincere you are in your sentiment. I'll reply to you >> > personally about the points that I consider to be red herrings and >> > ad hominem attacks so we don't taint the dicussion. If you don't >> > reply I'll know you were not being sincere. >> >> Jumping at your every demand is not a prerequisite for being sincere. > > I spent a lot of time writing that mail. Not sincere it is then. That kind of exchange is what you should show some of your personal friends and ask them whether it will likely lead to the desired understanding and ultimately reaction in the reader. Because that is what communication is about. Of course, one can try bypassing understanding and directly aim for a particular reaction: that is being manipulative. You are hardly in danger of being manipulative: that would require a basic understanding of people. So all you can really aim for is understanding: presenting your best case. Forget about "rhetorics" and the like: you suck at them, and a technical audience is easily annoyed by them even when they are employed well. And if a calm presentation does not lead others to the same conclusion that you would draw, deal with the consequences. Throwing tantrums will only bias people against you when you have the next case to present. -- David Kastrup -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html