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

Re: [RFC] How to accellerate the patch flow (or should we?)

From
Patrick Steinhardt <ps@pks.im>
Date
Sep 29, 2025, 23:25 UTC
Message-ID
<aNsVT_OWOCAB3fzO@pks.im>
In-Reply-To
<xmqqqzvo6fmw.fsf@gitster.g>
On Mon, Sep 29, 2025 at 03:46:47PM -0700, Junio C Hamano wrote:
Show 16 quoted lines
> Patrick Steinhardt <ps@pks.im> writes:
> 
> > Despite the potential awkwardness I have to wonder whether this would
> > even help us with the goal to speed up the overall process. To me it
> > rather feels like there's another step now that a patch series has to go
> > through, so my naive expectation is that it will rather slow the process
> > down even more.
> >
> > Am I missing something?
> 
> The above is an effort to reduce the chance/risk that the maintainer
> is *not* made aware of the fact that a topic has already been well
> reviewed, or the latest reroll has addressed all the issues
> previously have pointed out and the reviewers are happy with its
> shape, and ready to be merged to 'next', just left in 'seen' labeled
> with "Will merge to 'next'?", etc.

Ah, okay, that makes more sense then. So basically, reviewers should more explicitly state their overall opinion on a patch series so that it becomes easier for you to figure out the current state at a glance?

Patrick
Previous: Junio C HamanoNext: Junio C Hamano
Message 7 of 17 in “[RFC] How to accellerate the patch flow (or should we?)”
  1. Junio C HamanoSep 26, 2025
  2. Taylor BlauSep 27, 2025
  3. Junio C HamanoSep 28, 2025
  4. Taylor BlauSep 28, 2025
  5. Patrick SteinhardtSep 29, 2025
  6. Junio C HamanoSep 29, 2025
  7. Patrick SteinhardtSep 29, 2025
  8. Junio C HamanoOct 1, 2025
  9. Taylor BlauSep 30, 2025
  10. Junio C HamanoSep 30, 2025
  11. Kristoffer HaugsbakkSep 29, 2025
  12. Ben KnobleSep 29, 2025
  13. Patrick SteinhardtSep 29, 2025
  14. Patrick SteinhardtSep 29, 2025
  15. Taylor BlauSep 30, 2025
  16. Kristoffer HaugsbakkSep 29, 2025
  17. Junio C HamanoSep 29, 2025

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.