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

Re: RFC: a plugin architecture for git extensions?

From
Jon Seymour <jon.seymour@gmail.com>
Date
May 6, 2011, 06:20 UTC
Message-ID
<BANLkTi=zrWR0GAm6n1Gs9XDCR6kXtjDW0A@mail.gmail.com>
In-Reply-To
<7vbozg4eqw.fsf@alter.siamese.dyndns.org>
On Fri, May 6, 2011 at 2:47 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 8 quoted lines
> Jon Seymour <jon.seymour@gmail.com> writes:
>> It would be good if something like:
>>
>>     unzip -d $(git --plugins-dir) foobar.zip
>>
>> installed scripts, info files and man pages into a place where git
>> would find them and then have git foobar start working without any
>> additional effort by the package author or user.
> That should be doable without any elaborate "plugin management".  We only
> need to enhance the git potty and help system to look for things in a set
> of new directories, and have these unzip installation put their stuff
> there.
I do agree - plugin management is superfluous to current requirements.
Show 35 quoted lines
>>>
>>> *1* I admit that I didn't read all of them carefully, as I was repelled by
>>> them as soon as I saw phrases like "for people who can grok this concept".
>>
>> Junio: at least quote me accurately. I actually wrote:
>>
>> "Contributors who grok the concept as I conceive it are welcome to
>> submit pull requests."
>>
>> I am a little mystified why use of the word "grok" in this way, given the
>> circumstances, caused you to be "repelled".
>
> What repelled me was not any particular word (and that is exactly why I
> did not even bother to "quote") but your general attitude in the
> discussion.  Your tone throughout the discussion appeared at least to me
> that you thought anybody who did not agree with you was incapable of
> understanding something so obvious and clearly right, and only those who
> could "grok" it deserved to join the discussion.  We occasionally have
> seen such people on this list in the past, but luckily not very often.
>
> I am not saying that your thinking should always start from "I could be
> wrong".  However, I do not think "What is so hard about the concept ...?"
> is the question you should be asking others before asking yourself "Is
> there a better way I could have explained this idea I want others to agree
> with?  The reason why they are still not on the same page as I am could
> well be because all of them are morons, but it may be possible that it is
> because the way I have explained my idea to them was not optimal.  Perhaps
> I did not present the motivation and the background well enough to justify
> that the problem I am trying to solve is worth solving, before throwing my
> idea on how to solve it".
>
> After all, different people have different needs and expectations.  The
> discussion on a particular _solution_ can only start after you get people
> on board and share the sense of _need_ to solve something common.
>
Ok, well thanks for taking the time to explain what you really meant.

I agree that I have come across as arrogant; I reacted badly to what I considered to be insults being heaped in my direction by some. However, I did myself and my ideas no favors by treating such criticism with the public disdain that I did.

I also agree that I did a lousy job explaining the concepts let alone convincing others of their merits.

Finally, I agree that it would be more productive for me to be more sensitive to what is agreed to be a common need and to try to restrict my proposed solutions to exactly those needs.

I would appreciate any feedback you (or others) have about:
    http://permalink.gmane.org/gmane.comp.version-control.git/172419
In particular, I would be interested in feedback about how to best support:
- multiple extensions - do we want support installing extensions in
their own directories, per Pau's suggestion or simply allow them to
write to a common directory?
- multiple extension directories - how to support Jonathan's
requirement to allow user specific extension directories?

I have some ideas about how to do this which I will propose in a patch over the next few weeks, but any input I have now would be useful.

Regards,
jon.
Previous: Junio C HamanoNext: Jonathan Nieder
Message 69 of 105 in “RFC: a plugin architecture for git extensions?”
  1. Jon SeymourApr 27, 2011
  2. Jonathan NiederApr 27, 2011
  3. Jon SeymourApr 27, 2011
  4. Junio C HamanoApr 27, 2011
  5. Jon SeymourApr 27, 2011
  6. Junio C HamanoApr 27, 2011
  7. Jon SeymourApr 27, 2011
  8. Jon SeymourApr 27, 2011
  9. Junio C HamanoApr 27, 2011
  10. Jon SeymourApr 27, 2011
  11. Jon SeymourApr 27, 2011
  12. Michael J GruberApr 27, 2011
  13. Jon SeymourApr 27, 2011
  14. Jon SeymourApr 27, 2011
  15. Motiejus JakštysApr 27, 2011
  16. Jon SeymourApr 27, 2011
  17. Motiejus JakštysApr 27, 2011
  18. Carlos Martín NietoApr 27, 2011
  19. Jon SeymourApr 27, 2011
  20. Fredrik GustafssonApr 27, 2011
  21. Jon SeymourApr 27, 2011
  22. Pau Garcia i QuilesApr 27, 2011
  23. Jon SeymourApr 27, 2011
  24. Ævar Arnfjörð BjarmasonApr 27, 2011
  25. Jon SeymourApr 27, 2011
  26. Enrico WeigeltMay 13, 2011
  27. Andreas EricssonApr 27, 2011
  28. Jon SeymourApr 27, 2011
  29. Felipe ContrerasApr 27, 2011
  30. Jon SeymourApr 27, 2011
  31. Andreas EricssonApr 27, 2011
  32. Jon SeymourApr 27, 2011
  33. Jon SeymourApr 27, 2011
  34. A Large Angry SCMApr 27, 2011
  35. Jon SeymourApr 28, 2011
  36. Jon SeymourApr 28, 2011
  37. Jon SeymourApr 28, 2011
  38. Jon SeymourApr 28, 2011
  39. david@lang.hmApr 28, 2011
  40. Jon SeymourApr 29, 2011
  41. Motiejus JakštysApr 27, 2011
  42. Motiejus JakštysApr 27, 2011
  43. Junio C HamanoApr 27, 2011
  44. Junio C HamanoApr 27, 2011
  45. Drew NorthupApr 27, 2011
  46. Joey HessApr 27, 2011
  47. Drew NorthupApr 27, 2011
  48. Junio C HamanoApr 27, 2011
  49. Jonathan NiederApr 27, 2011
  50. Jon SeymourApr 27, 2011
  51. Andreas EricssonApr 28, 2011
  52. Junio C HamanoApr 27, 2011
  53. Jonathan NiederApr 27, 2011
  54. Junio C HamanoApr 28, 2011
  55. Jon SeymourApr 28, 2011
  56. Jon SeymourApr 28, 2011
  57. david@lang.hmApr 28, 2011
  58. Jon SeymourApr 28, 2011
  59. Jon SeymourApr 28, 2011
  60. Jon SeymourApr 28, 2011
  61. Andreas EricssonApr 28, 2011
  62. Jon SeymourApr 28, 2011
  63. Jonathan NiederApr 28, 2011
  64. Jon SeymourApr 28, 2011
  65. David AguilarMay 5, 2011
  66. Junio C HamanoMay 5, 2011
  67. Jon SeymourMay 5, 2011
  68. Junio C HamanoMay 6, 2011
  69. Jon SeymourMay 6, 2011
  70. Jonathan NiederMay 6, 2011
  71. Jonathan NiederMay 6, 2011
  72. Jon SeymourMay 6, 2011
  73. Jonathan NiederMay 6, 2011
  74. Jon SeymourMay 6, 2011
  75. Jonathan NiederMay 6, 2011
  76. Jon SeymourMay 8, 2011
  77. Jonathan NiederMay 8, 2011
  78. Jon SeymourMay 8, 2011
  79. Jeff KingMay 6, 2011
  80. John SzakmeisterMay 7, 2011
  81. Jon SeymourMay 8, 2011
  82. Jeff KingMay 9, 2011
  83. Jon SeymourMay 9, 2011
  84. Jeff KingMay 9, 2011
  85. Jon SeymourMay 9, 2011
  86. Jeff KingMay 9, 2011
  87. Jon SeymourMay 9, 2011
  88. Jon SeymourMay 9, 2011
  89. Jeff KingMay 9, 2011
  90. Jon SeymourMay 9, 2011
  91. Jeff KingMay 9, 2011
  92. Jon SeymourMay 9, 2011
  93. Jon SeymourMay 8, 2011
  94. Miles BaderMay 9, 2011
  95. David AguilarMay 14, 2011
  96. Andreas EricssonApr 28, 2011
  97. Jon SeymourApr 28, 2011
  98. Pau Garcia i QuilesApr 28, 2011
  99. Jon SeymourApr 28, 2011
  100. Pau Garcia i QuilesApr 28, 2011
  101. Jon SeymourApr 28, 2011
  102. Jon SeymourApr 28, 2011
  103. Jon SeymourApr 28, 2011
  104. Motiejus JakštysApr 27, 2011
  105. Jon SeymourApr 27, 2011

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.