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

Re: [RFC/PATCH] point pull requesters to Git Git Gadget

From
Roberto Tyley <roberto.tyley@gmail.com>
Date
Mar 12, 2019, 23:08 UTC
Message-ID
<CAFY1edYQcWzYJXF6f_TRk4=bEMVnFXTAp=5u=TJ4XZ3UUd4EmA@mail.gmail.com>
In-Reply-To
<20190312213246.GA6252@sigill.intra.peff.net>

On Tue, 12 Mar 2019 at 21:34, Jeff King <peff@peff.net> wrote: ...

> We could continue to mention _both_ tools, but it's probably better to
> pick one in order to avoid overwhelming the user with choice. After all,
> one of the purposes here is to reduce friction for first-time or
> infrequent contributors. And there are a few reasons to prefer GGG:
That's fair enough - I haven't committed to submitGit for 2 years
(it's continued to work without incident for most of that time I
think!). I would be prepared to spend more time on it if it was
important to people - or, heavens forfend, I could be paid to do so :)
 - but I have a lot of projects (not just software ones!) and
submitGit kind of fell to the bottom of the pile. I wasn't aware of
https://gitgitgadget.github.io/ but it looks good!
>   1. submitGit seems to still have a few rough edges. E.g., it doesn't
>      munge timestamps to help threaded mail readers handled out-of-order
>      delivery.
Yup, very true.
>   2. Subjectively, GGG seems to be more commonly used on the list these
>      days, especially by list regulars.

That's probably true too, though my interest with submitGit was more driven by helping early/first-time contributors than regulars. Though I'm sure GGG works well, in an ideal world it would be interesting to get a perspective from a cohort of those kind of users about what kind of flow works best for them - although, as I haven't been following development, maybe this has already been done?

>   3. GGG seems to be under more active development (likely related to
>      point 2).
Definitely true!
> I feel a little bad sending this, because I really value the work that
> Roberto has done on submitGit. So just dropping it feels a bit
> dismissive.

Oh, you're very kind, that's ok! Very glad submitGit could help for a while, sounds like it was a good proof that GitHub could become part of the contribution process.

Roberto
Previous: Jeff KingNext: Jeff King
Message 2 of 28 in “point pull requesters to Git Git Gadget”
  1. point pull requesters to Git Git GadgetJeff King, Mar 12, 2019
  2. Roberto TyleyMar 12, 2019
  3. Jeff KingMar 13, 2019
  4. Johannes SchindelinMar 13, 2019
  5. Junio C HamanoMar 13, 2019
  6. Jeff KingMar 13, 2019
  7. Jeff KingMar 13, 2019
  8. Johannes SchindelinMar 14, 2019
  9. Jeff KingMar 15, 2019
  10. Johannes SchindelinMar 15, 2019
  11. Jeff KingMar 15, 2019
  12. Junio C HamanoMar 18, 2019
  13. Jeff KingMar 18, 2019
  14. Thomas GummererMar 18, 2019
  15. Jeff KingMar 18, 2019
  16. Junio C HamanoMar 19, 2019
  17. Ævar Arnfjörð BjarmasonMar 18, 2019
  18. Johannes SchindelinMar 13, 2019
  19. Junio C HamanoMar 13, 2019
  20. Junio C HamanoMar 13, 2019
  21. Junio C HamanoMar 13, 2019
  22. Jeff KingMar 13, 2019
  23. GitGitGadget on github.com/git/git?, was Re: [RFC/PATCH] point pull requesters to Git Git GadgetJohannes Schindelin, Mar 14, 2019
  24. Duy NguyenMar 14, 2019
  25. Jeff KingMar 15, 2019
  26. Johannes SchindelinMar 15, 2019
  27. Ævar Arnfjörð BjarmasonMar 15, 2019
  28. Jeff KingMar 15, 2019

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.