archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <>
To: Theodore Ts'o <>,
	Felipe Contreras <>
Cc: Max Horn <>, Junio C Hamano <>,
Subject: Re: My patches
Date: Fri, 18 Oct 2013 10:49:48 -0500	[thread overview]
Message-ID: <5261589c855ea_30ce11dbe78d3@nysa.notmuch> (raw)
In-Reply-To: <>

Theodore Ts'o wrote:
> On Fri, Oct 18, 2013 at 06:41:41AM -0500, Felipe Contreras wrote:
> > > And I hazard to guess that the vast majority agree with Junio on this (based,
> > > again, on email evidence). Not with you.
> > 
> > That is irrelevant, and a fallacy. The vast majority of people thought the
> > Earth was the center of the universe, and they were all wrong.
> > 
> > It's called ad populum fallacy, look it up. Wether the majority of Git
> > developers agree that there's something more than a disagreement is irrelevant,
> > their opinion doesn't change the truth.
> Look, the problem is that you insist on being "right", even on matters which
> may be more about taste and preference than anything that can be proven
> mathematically.

I don't insist on being right, I have an opinion and I voice it, there is
nothing wrong with that. If the other side agrees there's a difference of
opinion, that's the end of the discussion.

I would say it's actually the other side that insists on being right, and
that's the problem; they don't agree it's a difference in opinion, from their
point of one side is right, and the other side is wrong, and that's what causes
their frustration.

Ask Junio if he thinks it's simply a matter of a difference in opinion. He
pretty much already said it's not.

> Worse, you insist on trying to convince people even when it might be better
> to just give up and decide that maybe something not's worth the effort to get
> the last word in.  This is how we get to centithreads.  If every time someone
> disagrees, you insist on replying,

This is how it goes:

 1) Side A
 2) Side B

 3) Side A
 4) Side B

 5) Side A
 6) Side B

At any point in time side B could stop replying, sure, but so could side A.

Why do you blame ME for replying, and not the other side, for replying to my

Presumably because right before reply 4), side A thought the discussion was
wortwhile, and something happened in 5) that changed their opinion, and now
side B becomes a problematic person. And since you are friends with side A, you
take their side.

> and then if people give up in disgust, you then try to use that as "proof"
> that you must be right,

Show me *one* instance when I have done so. I have never used silence as
evidence of anything.

> Sometimes a question is important enough that it's worth doing this.
> But I'd suggest to you that you should ask yourself whether you're
> doing it too often.
> After all, this is open source.  If you are convinced that you are
> right, and everyone else in the community is wrong, it is within your
> power to fork the code base, and to prove us wrong by creating a
> better product.

Don't worry, that is *exactly* what I plan to do.

> The fallocate NO_HIDE_STALE flag is a good example of that; it's used
> in production on thousands and thousands of servers by Google and Tao
> Bao, but since there was strong opposition on the ext4 list, we've
> kept it as an out-of-tree patch.  Note what I did not do.  I did not
> force the patch in, even though it might be within my power as the
> maintainer; nor did I try to convince people over and OVER and OVER
> again about the rightness of my position, and turn it into a
> centithread.

My patches are not good just for me or my company, they are good for everyone.

Have you actually looked at any of them?

> > My claim is that all I did was disagree with Junio. You can invalidate that
> > claim easily by providing *a single* example where I did more than
> > disagree.
> The problem is when you disagree with a number of people (not just
> Junio), and you are, in my opinion, overly persistent.

But that's not what Junio said. This is the second time you defend Junio by
assuming his position is exactly the opposite.

Junio doesn't think it's just a disagreement, Junio doesn't think I'm just
being persistent, Junio is saying I can't be worked with.

The interesting thing is that when Junio agrees with the change, he can work
with me, when I agree my change is not good, the same, but suddenly when I
don't agree, then I'm not good to work with. See the pattern?

> We can argue whether you've stepped over the line in terms of impugning
> people's motives or sanity, but that's not necessarily the most important
> issue.  People sometimes step over the line, and while that's unfortunate,
> it's when it becomes a persistent pattern, and it happens frequently enough,
> that it becomes a real problem.

Have I ever impugned people's motives or sanity? Please, show me where I did that.

> Alternatively, if you are right that Junio is mad,

I didn't say Junio is mad, I said he got mad.

:  carried away by intense anger :  furious <mad about the delay>

> and he's being capriciously insulting, then I'm sure that when you establish
> your own fork, lots of developers will come flocking to your flag.  If they
> do not, then perhaps you might want to take that as some objective evidence
> that the community is perhaps, more willing to work with him, then they are
> to work with you.

If you know anything about rationality you know that correlation doesn't prove
causation. So no, it would not be objective evidence.

Felipe Contreras

  reply	other threads:[~2013-10-18 16:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-12  7:24 My patches Felipe Contreras
2013-10-12 16:18 ` Philip Oakley
2013-10-12 22:33   ` Felipe Contreras
2013-10-14 17:42 ` Junio C Hamano
2013-10-14 21:40   ` Felipe Contreras
2013-10-17 19:54     ` Junio C Hamano
2013-10-17 21:44       ` Felipe Contreras
2013-10-18 11:21         ` Max Horn
2013-10-18 11:41           ` Felipe Contreras
2013-10-18 15:30             ` Theodore Ts'o
2013-10-18 15:49               ` Felipe Contreras [this message]
2013-10-18 16:59               ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5261589c855ea_30ce11dbe78d3@nysa.notmuch \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).