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

Re: [PATCH v2 01/17] contrib: remove outdated README

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
May 14, 2014, 21:26 UTC
Message-ID
<5373df8424a35_592416ad2f8c7@nysa.notmuch>
In-Reply-To
<20140514202646.GE2715@sigill.intra.peff.net>
Jeff King wrote:
Show 7 quoted lines
> On Wed, May 14, 2014 at 02:35:08PM -0500, Felipe Contreras wrote:
> 
> > Prior to his decision there were no complaints about my "manners" since
> > I returned. It was his *TECHNICAL* decision that triggered this.
> 
> There have been several complaints about your behavior since you
> returned[1,2,3,4],
> [1] http://article.gmane.org/gmane.comp.version-control.git/247108

This is not a complaint, you are merely saying you are not interested in discussing with me without mentioning any bad behavior at that time.

And this is not related to remote-hg/bzr.
> [2] http://article.gmane.org/gmane.comp.version-control.git/247121

This is a complaint without pointing out what are the specific instances of bad behavior, present or past.

> [4] http://article.gmane.org/gmane.comp.version-control.git/247168

This is not a complaint about bad behavior. Unless you think making a bet is bad behavior.

And this is unrelated to remote-hg/bzr.
> [3] http://article.gmane.org/gmane.comp.version-control.git/248000

This is a complaint about a factual statement, a prediction about the future that turned out to be true. Unflattering factual predictions can hardly be considered "bad behavior"

And this is unrelated to remote-hg/bzr.
Show 5 quoted lines
> I have not paid all that close attention to this remote-hg contrib
> argument. Maybe you are 100% right and Junio is wrong and lying and
> cannot back up his decision, but somehow needs to cover it up through
> rhetoric. But that does not at all match my past experiences with
> Junio's behavior.

The fact that something hasn't happened in the past doesn't mean it's not happening right now.

I am still waiting for Junio's answer to *one* question.

If your expectation about Junio is correct, it should be easy for him to say "Felipe is wrong, here's where I explained in full my rationale of the technical issues that triggered my decision to demote the remote helpers, and as you can see, the importance of the decision is well matched by the detail of my explanation". But he is not doing that, is he?

It would be easy for him to do that, why isn't he doing so? You are giving him a free pass.

Show 5 quoted lines
> I can understand that it hurts to be called a troll. I really do believe
> you are trying your best to improve git. But I hope you also understand
> that in terms of the time and emotional drains on other participants,
> from our perspective interacting with you is quite similar to
> interacting with a troll.

Yes, I can understand that, and I would understand if Junio said I was acting *like* a troll. But he unequivocally said I was a troll, even when I asked for clarification.

Maybe that's acceptable to you. That's where I draw the line.
> Your continued arguing on this topic does not seem like it is going
> anywhere,

I'm not arguing on this topic any more. I gave up on Junio trying to answer my *one* question. The remote helpers will not graduate because Junio said so, and he didn't explain his reasoning. That's an unfortunate fact.

All I'm trying now is to move foward, by:
 1) Add a warning about the new location of remote-helpers
 (Junio chose to argue instead)
 2) Remove the remote-helpers and replace them with warning stubs
 ("Somehow" the patches didn't reach the mailing list)
 3) Make sure everything is in place for users and packagers to use the
    new location (it can't never be as good as graduating to the core)
 
 (The fact that Junio is preventing 1) and 2) doesn't help)
Additionally:
 4) Correct any misconceptions in the lingering threads
> and I believe is wasting time and hurting the atmosphere of
> the list. Please stop.

Tell other people to stop. I am merely replying to misconstrued conceptions. If other people stop, so would my replies.

I am not going to let the record about such an important decision be tainted by these misconceptions.

Show 5 quoted lines
> [5] Even though you were previously asked to leave, I believe people
>     on the list gave interacting with you a fair shot in the past month
>     or two. And we somehow still ended up at the same place.  That's
>     just my perception, of course. I'd invite anybody watching to form
>     their own opinions.

And that's entirely Junio's fault for making a haste decision, and giving no rationale about it.

Given all the time I've spent on these tools, I wasn't willing to let my work be threated like crap by Junio. I deserved an explanation, and if he wasn't going to give one, I'd rather leave the project trying to get one (even if that meant behaving in a way other people considered "bad").

And BTW, I still think git-archimport and git-quiltimport should be demoted from the core, and I think the contrib area should be cleaned up, many of the tools removed, and others maintained out-of-tree. Do not think I sent those patches to "troll".

Cheers.

P.S. While we disagree on many topics, I do appreciate the fact that you are never condescending and try to be honest, and when it becomes difficult to do that, you explain so and leave the discussing. Never letting your ego get in the way of a clear record. Which is more than I can say about Junio after this incident.

-- 
Felipe Contreras
Previous: Jeff KingNext: Junio C Hamano
Message 15 of 42 in “contrib: cleanup”
  1. 00/17 contrib: cleanupFelipe Contreras, May 9, 2014
  2. 01/17 contrib: remove outdated READMEFelipe Contreras, May 9, 2014
  3. Junio C HamanoMay 9, 2014
  4. Felipe ContrerasMay 9, 2014
  5. Martin LanghoffMay 13, 2014
  6. Junio C HamanoMay 13, 2014
  7. Felipe ContrerasMay 13, 2014
  8. Junio C HamanoMay 13, 2014
  9. Martin LanghoffMay 13, 2014
  10. Felipe ContrerasMay 13, 2014
  11. Philippe VaucherMay 14, 2014
  12. Felipe ContrerasMay 14, 2014
  13. Martin LanghoffMay 14, 2014
  14. Jeff KingMay 14, 2014
  15. Felipe ContrerasMay 14, 2014
  16. Junio C HamanoMay 14, 2014
  17. Felipe ContrerasMay 14, 2014
  18. Martin LanghoffMay 14, 2014
  19. Felipe ContrerasMay 14, 2014
  20. Junio C HamanoMay 15, 2014
  21. Felipe ContrerasMay 16, 2014
  22. William GiokasMay 16, 2014
  23. Felipe ContrerasMay 16, 2014
  24. William GiokasMay 16, 2014
  25. Felipe ContrerasMay 16, 2014
  26. Felipe ContrerasMay 13, 2014
  27. 02/17 contrib: remove 'vim'Felipe Contreras, May 9, 2014
  28. 03/17 contrib: remove 'emacs'Felipe Contreras, May 9, 2014
  29. 04/17 contrib: remove 'diffall'Felipe Contreras, May 9, 2014
  30. Tim HeniganMay 9, 2014
  31. 05/17 contrib: remove 'hg-to-git'Felipe Contreras, May 9, 2014
  32. 07/17 contrib: remove 'stats'Felipe Contreras, May 9, 2014
  33. 08/17 contrib: remove 'convert-objects'Felipe Contreras, May 9, 2014
  34. 09/17 contrib: remove 'git-shell-commands'Felipe Contreras, May 9, 2014
  35. 10/17 contrib: reomve 'thunderbird-patch-inline'Felipe Contreras, May 9, 2014
  36. 11/17 contrib: remove 'workdir'Felipe Contreras, May 9, 2014
  37. 12/17 contrib: remove 'svn-fe'Felipe Contreras, May 9, 2014
  38. 13/17 contrib: remove 'rerere-train'Felipe Contreras, May 9, 2014
  39. 14/17 contrib: remove 'remotes2config'Felipe Contreras, May 9, 2014
  40. 15/17 contrib: remove 'persistent-https'Felipe Contreras, May 9, 2014
  41. 16/17 contrib: remove 'git-resurrect'Felipe Contreras, May 9, 2014
  42. 17/17 contrib: remove 'contacts'Felipe Contreras, May 9, 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.