Re: Pain points in Git's patch flow

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 16, 2021, 20:25 UTC
Message-ID: <xmqqblaekmd9.fsf@gitster.g>
In-Reply-To: <xmqqfszqko0k.fsf@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

Show 12 quoted lines

> So here is a real-life example.
>
> Let's say somebody is looking at a "gentle ping" [*1*]
>
> znh> The patch seems to have fallen into the crack.
> zhn> Jeff and Junio, willing to help?
>
> How would we figure out what happened to the patch today without
> visiting patchwork would be:
> ...
> Now, how can patchwork improve the above reviewer experience, out
> of the box and possibly with new helpe rools around it?

Also, it would be ideal if it is made easy for willing reviewers with excess bandwidth to preemptively find and review patches that need reviewing. I think your original write-up upthread covered this use case sufficiently.

Thanks.

$ 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.