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

Re: RFC: Moving git-gui development to GitHub

From
Jakub Narebski <jnareb@gmail.com>
Date
Oct 26, 2019, 18:25 UTC
Message-ID
<86k18rbbyz.fsf@gmail.com>
In-Reply-To
<CABPp-BEHy8c3raHwf9aFXvXN0smf_WwCcNiYxQBwh7W6An60qQ@mail.gmail.com>
Elijah Newren <newren@gmail.com> writes:
Show 7 quoted lines
> On Thu, Oct 24, 2019 at 2:45 AM Pratyush Yadav <me@yadavpratyush.com> wrote:
>>
>> I recently had some discussions with Dscho about whether it is a better
>> idea to use GitHub for development instead of email [0]. His argument
>> was that GitHub makes it easier for newcomers to contribute, since more
>> people are familiar with GitHub compared to mailing lists. Also, it is
>> somewhat difficult to set up an email-based workflow.
[...]
Show 5 quoted lines
> GitHub is great for ease of creating new repos, learning about other
> developers, finding similar projects, creation of webhooks, etc.  But
> it's *awful* for code review.  Gerrit is a lot better at code reviews
> (though still has problems); so maybe dealing with both GitHub and
> Gerrit would be reasonable.
[...]
Show 8 quoted lines
> Email is a horrible medium for sending/receiving
> changes, but at least it gets the overall code review model right
> (commit-messages-are-first-order-objects-that-can-be-reviewed,
> review-individual-commits, merge-per-topic, cover-letter included,
> range-diff for high-level comparison of different iterations,
> reversing-commit-order-display-based-on-author-timestamps-is-NOT-forgivable,
> Change-IDs-are-ugly, magic-refs-are-disgusting, etc.), something no
> GUI tool (yet) does to my knowledge.

I agree with that. You need then to decide whether it is better to have it easier for beginners to contribute, or is it better to have it easier to review code. What are the pain points?

Another source worth looking into is "Patches carved into stone tablets, why the Linux kernel developers rely on plain text email instead of using “modern” development tools." presentation by Greg KH from 2016[1][2]. But remember that git-gui is not Linux kernel; what works for one might not work for the other.

It is unfortunate that we have no tools described in "Patches carved into developer sigchains"[3] wishfull blog post by Konstantin Ryabitsev...

[1]: https://kernel-recipes.org/en/2016/talks/patches-carved-into-stone-tablets/ [2]: https://www.slideshare.net/ennael/kernel-recipes-2016-patches-carved-into-stone-tablets [3]: https://people.kernel.org/monsieuricon/patches-carved-into-developer-sigchains

Regards, -- Jakub Narębski

Previous: Pratyush YadavNext: Konstantin Ryabitsev
Message 11 of 20 in “RFC: Moving git-gui development to GitHub”
  1. Pratyush YadavOct 23, 2019
  2. Junio C HamanoOct 24, 2019
  3. Birger Skogeng PedersenOct 24, 2019
  4. Denton LiuOct 24, 2019
  5. Pratyush YadavOct 24, 2019
  6. Pratyush YadavOct 24, 2019
  7. Birger Skogeng PedersenOct 25, 2019
  8. Pratyush YadavOct 25, 2019
  9. Elijah NewrenOct 24, 2019
  10. Pratyush YadavOct 25, 2019
  11. Jakub NarebskiOct 26, 2019
  12. Konstantin RyabitsevOct 28, 2019
  13. Elijah NewrenOct 30, 2019
  14. Birger Skogeng PedersenNov 20, 2019
  15. Elijah NewrenNov 20, 2019
  16. Pain points in PRs [was: Re: RFC: Moving git-gui development to GitHub]SZEDER Gábor, Apr 19, 2021
  17. Junio C HamanoApr 19, 2021
  18. Son Luong NgocApr 20, 2021
  19. Junio C HamanoApr 20, 2021
  20. Felipe ContrerasApr 22, 2021

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.