git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Should git-remote-hg/bzr be part of the core?

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
May 12, 2014, 12:48 UTC
Message-ID
<5370c32d7ffc7_168f13a72fc6b@nysa.notmuch>
In-Reply-To
<CAHVLzcmqdkf4fMTok+HsXcDOQ5Oz2QdZti3FuzgBUa2T6AWnfA@mail.gmail.com>
Paolo Ciarrocchi wrote:
Show 10 quoted lines
> On Mon, May 12, 2014 at 11:42 AM, Michael Haggerty <mhagger@alum.mit.edu>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.
Thanks.
> 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 important.

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
Previous: Felipe ContrerasNext: Paolo Ciarrocchi
Message 16 of 19 in “Should git-remote-hg/bzr be part of the core?”
  1. Felipe ContrerasMay 11, 2014
  2. Michael HaggertyMay 12, 2014
  3. Dennis KaarsemakerMay 12, 2014
  4. Felipe ContrerasMay 12, 2014
  5. Michael HaggertyMay 12, 2014
  6. Felipe ContrerasMay 12, 2014
  7. David KastrupMay 12, 2014
  8. Felipe ContrerasMay 12, 2014
  9. Michael HaggertyMay 12, 2014
  10. Felipe ContrerasMay 12, 2014
  11. David KastrupMay 12, 2014
  12. Felipe ContrerasMay 12, 2014
  13. Felipe ContrerasMay 12, 2014
  14. Stefan BellerMay 12, 2014
  15. Felipe ContrerasMay 12, 2014
  16. Felipe ContrerasMay 12, 2014
  17. Paolo CiarrocchiMay 12, 2014
  18. Stefan BellerMay 12, 2014
  19. Felipe ContrerasMay 12, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.