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
Junio C Hamano <gitster@pobox.com>
Date
Sep 29, 2025, 22:12 UTC
Message-ID
<xmqq4isk7vrv.fsf@gitster.g>
In-Reply-To
<87792693-58d9-4047-beae-38aa4c59ed41@app.fastmail.com>
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
Show 9 quoted lines
>> The time taken during 7. is pretty much fixed and unless we are
>> willing to sacrifice the quality of the end result, cannot
>> reasonably be shortened (note that this is based on the assumption
>> that "find any remaining bugs while it is in 'next' before it hits
>> 'master'" philosophy is working, but we have never run experiments
>> to shorten this to say 3 days to see if we see more bugs on 'master'
>> yet).
>
> Maybe pure documentation changes could cook for less than seven days.

Yup, that kind of adjustment at the maintainer's discretion has already been applied, depending on the nature of a topic. Some truly trivial typofixes may not even go through 'next' but get applied to 'master' directly.

Thanks.
Previous: Kristoffer Haugsbakk
Message 17 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.