archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <>
To: Paolo Ciarrocchi <>,
	Michael Haggerty <>
Cc: "Felipe Contreras" <>,
	"Git Mailing List" <>,, "Richard Hansen" <>,
	"Torsten Bögershausen" <>,
	"Antoine Pelisse" <>,
	"Christophe Simonis" <>,
	"Dusty Phillips" <>, "Jeff King" <>,
	"John Keeping" <>
Subject: Re: Should git-remote-hg/bzr be part of the core?
Date: Mon, 12 May 2014 07:48:45 -0500	[thread overview]
Message-ID: <5370c32d7ffc7_168f13a72fc6b@nysa.notmuch> (raw)
In-Reply-To: <>

Paolo Ciarrocchi wrote:
> On Mon, May 12, 2014 at 11:42 AM, Michael Haggerty <>wrote:
> > Felipe, you seem to have so much potential.  If you would put as
> > much effort in conducting social interactions as you do in coding,
> > the whole balance would change entirely, and any software project
> > would be happy to have you.  With all my heart I truly wish you the
> > best in your future endeavors.
> I really *love* this paragraph. Felipe, you are a brilliant developer
> and you put a lot of work trying to improve GIT.


> While I agree with you the this project is managed in a bit conservative
> way

Only a bit? I don't think I've been involed in a more conservative open
source project.

> you should really improve how you communicate with other developers,
> it's such a pity your contributions are some times not included in
> git.git just because of your attitude.

But that's a theory. You don't *know* that they would have been included
had I used a different attitude.

In fact, people have contacted me privately saying similar things, and
I'll give you the same challenge I gave them. If you think a different
attitude would get my patches in, how about *you* write the commit
messages and the discussions for one of my stuck patch series. I'll send
the mails as if I had written the content.

If you are right, the different attitude would make the patches land in
no time. I still think it's not right for patches to be rejected simply
because of attitude, but I would accept you were right.

But I think you already know that won't happen, the patches still won't
get in, not because of the attitude, but because of what they are trying
to do: change things.

So if I *know* certain feature would be useful for Git users, I've
listened to all the comments, and addressed all the problems, why would
I give up on those patches? Why would I work on something more boring
that won't benefit users as much but would have higher chances of
getting in?

I'm doing this on my own free time, I can choose to do whatever I want,
in whatever way I want, so no, I'll keep working on what I think is

If you really think the patches can be accepted with a different
attitude, by all means, let's do the experiment and find out.

Felipe Contreras

  parent reply	other threads:[~2014-05-12 12:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11 23:34 Should git-remote-hg/bzr be part of the core? Felipe Contreras
     [not found] ` <>
2014-05-12  7:42   ` Felipe Contreras
2014-05-12  8:12     ` Felipe Contreras
2014-05-12 10:28       ` Stefan Beller
2014-05-12 12:05         ` Felipe Contreras
2014-05-12  9:42 ` Michael Haggerty
2014-05-12 10:35   ` Dennis Kaarsemaker
2014-05-12 10:37   ` Felipe Contreras
2014-05-12 12:05     ` Michael Haggerty
2014-05-12 12:29       ` Felipe Contreras
2014-05-12 13:12         ` David Kastrup
2014-05-12 17:12           ` Felipe Contreras
2014-05-12 13:43         ` Michael Haggerty
2014-05-12 17:13           ` Felipe Contreras
2014-05-12 11:00   ` David Kastrup
     [not found]   ` <>
2014-05-12 12:48     ` Felipe Contreras [this message]
2014-05-12 13:45       ` Paolo Ciarrocchi
2014-05-12 16:13         ` Stefan Beller
2014-05-12 16:40         ` Felipe Contreras

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=5370c32d7ffc7_168f13a72fc6b@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).