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

Re: [PATCH 2/2] Move sequencer to builtin

From
Stefano Lattarini <stefano.lattarini@gmail.com>
Date
Jun 9, 2013, 23:40 UTC
Message-ID
<51B51256.5060602@gmail.com>
In-Reply-To
<51B4F6CA.8020807@alum.mit.edu>
[Sorry for the full quote, but sometimes, repetita iuvant]
On 06/09/2013 11:42 PM, Michael Haggerty wrote:
Show 46 quoted lines
> On 06/09/2013 09:11 PM, Johan Herland wrote:
>> [...]
>> FWIW, I'd like to express my support for the opinions expressed by
>> Jonathan, Jeff and Thomas. They accurately describe my impression of
>> these discussion threads.
> 
> I also agree.  In my opinion, Felipe, your abrasiveness, your disregard
> of project standards, and your eternal argumentativeness outweigh the
> benefit of your contributions, large though they may be.
> 
> Writing code is only a small part of keeping the Git project going.
> 
> * Reviewing code is an essential, more thankless, and therefore more
> precious, contribution.  Therefore the Git project has standards to make
> code review less unpleasant and more effective; for example: (1) patches
> shouldn't cause regressions; (2) commit messages have to be written to
> very high standards; (3) reviewers' comments should be accepted
> gratefully and taken very seriously.  Almost everybody in the Git
> community accepts these standards.  Felipe, you do not seem to.  The
> result is that reviewers' time and goodwill are wasted, and they
> justifiably feel unvalued.  We can't afford to misuse reviewers; they
> are the bedrock (and the bottleneck) of the project.
> 
> * Gaining and keeping contributors is important to maintaining the
> success of the project.  The mailing list is the main forum for the
> development community; therefore, it is important that the mailing list
> be a place where people display a high degree of technical excellence,
> but also respect for one another, friendliness (or at least a lack of
> hostility), and discussions that do turn into flame wars.  It is
> possible to have a profound technical disagreement without losing
> respect for the other side; contrariwise it is NOT acceptable to twist a
> technical disagreement into a personal attack, even by the slightest
> insinuation.  Felipe, in my opinion your participation in the mailing
> list lowers the tone dramatically, and will result in loss of other
> contributors and the failure to attract new contributors.
> 
> Felipe, I wish that you would devote a small fraction of your prodigious
> energy to the very difficult challenge of feeling empathy,
> understanding, and respect for the other members of the community.  But
> if things continue the way they have, I personally would, with sadness
> in my heart, prefer to forgo your patches in exchange for the more
> important benefit of a more collegial (and therefore overall more
> productive and sustainable) community.
> 
> Michael
> 

FWIW, from the meager but I hope not utterly irrelevant point of view of a non-contrib-but-not-clueless user as I am:

  *a complete and hear-felt +1 on what Michael said here*

Until a couple of months ago, skimming this list was mostly a real pleasure, and would often give me some valuable insight on the upcoming features/incompatibilities of Git, help me organize my own workflow as a Git user, and also steadily improve my understanding and command of netiquette in both "generic" mailing lists and Open Source and/or Free Software communities.

Now, when I open my mail and get to the "git" folder, I more and more end up asking myself:

  1. "What kind of flame am I going to have to see today?"; and
  2. "How much chaff will I have to navigate through to finally
      to get to interesting stuff (if any is actually left)?"
*To reiterate:*

Sadly, the environment of the Git mailing list has been steadily and slowly *sinking* -- sinking from being pleasant and useful and even "educational", into being annoying and frustrating and often somewhat toxic. I usually jeer and despise he who makes public accusations by simply adding his voice to the disapproval of the "community", but this time, I feel compelled to do exactly that:

  I do accuse Felipe's *attitude* to bring on and nourish such
  unpleasantness toxicity.  His technical merits and the possible
  qualities of his patches do *nothing* to remove or quell such
  issues.

Sorry for the extra potential controversy, but sometimes one has to speak up,

  Stefano
Previous: Michael HaggertyNext: Felipe Contreras
Message 47 of 82 in “Move sequencer”
  1. 0/2 Move sequencerFelipe Contreras, Jun 7, 2013
  2. 1/2 log-tree: remove dependency from sequencerFelipe Contreras, Jun 7, 2013
  3. 2/2 Move sequencer to builtinFelipe Contreras, Jun 7, 2013
  4. Duy NguyenJun 8, 2013
  5. Felipe ContrerasJun 8, 2013
  6. Duy NguyenJun 8, 2013
  7. Felipe ContrerasJun 8, 2013
  8. Duy NguyenJun 8, 2013
  9. Ramkumar RamachandraJun 8, 2013
  10. Duy NguyenJun 8, 2013
  11. Felipe ContrerasJun 8, 2013
  12. Ramkumar RamachandraJun 8, 2013
  13. Felipe ContrerasJun 8, 2013
  14. Duy NguyenJun 8, 2013
  15. Felipe ContrerasJun 8, 2013
  16. Jeff KingJun 9, 2013
  17. Ramkumar RamachandraJun 9, 2013
  18. Jeff KingJun 9, 2013
  19. Ramkumar RamachandraJun 9, 2013
  20. Felipe ContrerasJun 9, 2013
  21. Jeff KingJun 9, 2013
  22. Felipe ContrerasJun 9, 2013
  23. Ramkumar RamachandraJun 9, 2013
  24. Jeff KingJun 9, 2013
  25. Felipe ContrerasJun 9, 2013
  26. Felipe ContrerasJun 9, 2013
  27. Felipe ContrerasJun 9, 2013
  28. Felipe ContrerasJun 8, 2013
  29. Jonathan NiederJun 8, 2013
  30. Felipe ContrerasJun 8, 2013
  31. Jonathan NiederJun 8, 2013
  32. Felipe ContrerasJun 8, 2013
  33. Felipe ContrerasJun 8, 2013
  34. Jonathan NiederJun 9, 2013
  35. Felipe ContrerasJun 9, 2013
  36. Jonathan NiederJun 9, 2013
  37. Felipe ContrerasJun 9, 2013
  38. Jeff KingJun 9, 2013
  39. Felipe ContrerasJun 9, 2013
  40. Jeff KingJun 9, 2013
  41. Felipe ContrerasJun 9, 2013
  42. Jeff KingJun 9, 2013
  43. Felipe ContrerasJun 9, 2013
  44. Johan HerlandJun 9, 2013
  45. Felipe ContrerasJun 9, 2013
  46. Michael HaggertyJun 9, 2013
  47. Stefano LattariniJun 9, 2013
  48. Felipe ContrerasJun 10, 2013
  49. Bad attitudes and problems in the Git community (was: Re: [PATCH 2/2] Move sequencer to builtin)Stefano Lattarini, Jun 10, 2013
  50. Felipe ContrerasJun 10, 2013
  51. Martin von ZweigbergkJun 10, 2013
  52. Martin LanghoffJun 10, 2013
  53. Martin von ZweigbergkJun 10, 2013
  54. Felipe ContrerasJun 10, 2013
  55. Felipe ContrerasJun 10, 2013
  56. Andres FreundJun 11, 2013
  57. Felipe ContrerasJun 11, 2013
  58. Thiago FarinaJun 20, 2013
  59. Thomas RastJun 9, 2013
  60. Felipe ContrerasJun 9, 2013
  61. Ramkumar RamachandraJun 9, 2013
  62. Felipe ContrerasJun 9, 2013
  63. Jeff KingJun 9, 2013
  64. Ramkumar RamachandraJun 9, 2013
  65. Jeff KingJun 9, 2013
  66. Jonathan NiederJun 9, 2013
  67. Felipe ContrerasJun 9, 2013
  68. Ramkumar RamachandraJun 9, 2013
  69. Junio C HamanoJun 9, 2013
  70. Felipe ContrerasJun 10, 2013
  71. Junio C HamanoJun 10, 2013
  72. Felipe ContrerasJun 10, 2013
  73. Felipe ContrerasJun 10, 2013
  74. Matthieu MoyJun 10, 2013
  75. Ramkumar RamachandraJun 10, 2013
  76. Felipe ContrerasJun 10, 2013
  77. Felipe ContrerasJun 9, 2013
  78. Thomas RastJun 9, 2013
  79. Ramkumar RamachandraJun 9, 2013
  80. Felipe ContrerasJun 9, 2013
  81. Ramkumar RamachandraJun 8, 2013
  82. Felipe ContrerasJun 8, 2013

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.