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 30, 2025, 20:28 UTC
Message-ID
<xmqqbjmr4re6.fsf@gitster.g>
In-Reply-To
<aNw3VY7npZvHDU7i@nand.local>
Taylor Blau <me@ttaylorr.com> writes:
Show 5 quoted lines
> (As an aside, in the pseudo-patch I wrote above, the maintainer could
> choose to bypass the process entirely, since it would continue to be at
> their discretion. Perhaps that's just a semantics thing, since by
> merging the series the maintainer is implicitly providing their own
> "ack", without actually saying so.)

This is exactly the reason why I keep saying "being in 'seen' has no meaning other than I happened to have seen, not more than that". A topic queued in 'seen' by default has no "ack" from me or anybody.

Previous: Taylor BlauNext: Kristoffer Haugsbakk
Message 10 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.