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

Re: Ejecting things more aggressively out of 'seen'?

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 3, 2026, 19:29 UTC
Message-ID
<xmqqh5hx7ly1.fsf@gitster.g>
In-Reply-To
<aumNkxzE7wfa519p@pks.im>
Patrick Steinhardt <ps@pks.im> writes:
Show 12 quoted lines
>> An obvious alternative is to queue only topics for which I can, by
>> judging reviews on the list, at least say "Will merge to 'next'?"
>> with enough confidence.  It would reduce the size of 'seen' and the
>> friction felt by contributors when their topic is once queued on
>> 'seen' and later ejected unceremoniously through no fault of their
>> own, other than their topic being forgettable or uninspiring to
>> others.
>
> Wouldn't we lose the ability to integrate topics with one another early
> on to see how they interact? And it makes me wonder whether this will
> overall slow down progress of a patch series if it gets merged to "seen"
> at a later point.

Even when I see a topic was reviewed by humans and reviewers find it satisfactory standalone, it would not hit 'next' immediately. We are talking about topics that flow into 'seen' without attracting interest by people. Quite honestly, I do not think anybody should care if these topics do not play well with other such topics. It is the job of topic authors to make sure what they write meshes well with what is in flight, and not cluttering 'seen' with hopeless topics would help those serious authors who do their homework.

Once a topic is found interesting standalone, it is very much in the projects' interest to make sure it meshes well with other topics in flight. But not before.

> So maybe instead of someone saying that a patch series is ready, the bar
> should be that the patch series has gotten at least one human review
> that was somewhat favorable on the overall direction?

It has to be more like a trusted reviewer saying that it has potential to be a reasonable change.

We shouldn't require perfection from the get go and instead expect some more iterations after a topic hits 'seen'. But it is a promise to spend project resources on the topic to have it in 'seen'. It shouldn't be triggered by just a random drive-by commenter saying "I want moon and this is it" without any believable explanation.

Thanks.
Previous: Junio C HamanoNext: Matt Hunter
Message 15 of 25 in “What's cooking in git.git (Jul 2026, #12)”
  1. Junio C HamanoJul 27, 2026
  2. Phillip WoodJul 29, 2026
  3. Junio C HamanoJul 29, 2026
  4. Phillip WoodJul 29, 2026
  5. Junio C HamanoJul 29, 2026
  6. Phillip WoodAug 5, 2026
  7. Junio C HamanoAug 5, 2026
  8. Ejecting things more aggressively out of 'seen'?Junio C Hamano, Nov 2, 2026
  9. Patrick SteinhardtNov 2, 2026
  10. Junio C HamanoNov 2, 2026
  11. Phillip WoodNov 2, 2026
  12. Junio C HamanoNov 6, 2026
  13. Patrick SteinhardtNov 3, 2026
  14. Junio C HamanoNov 3, 2026
  15. Junio C HamanoNov 3, 2026
  16. Matt HunterJul 31, 2026
  17. Junio C HamanoJul 31, 2026
  18. Harald NordgrenJul 30, 2026
  19. Matt HunterJul 31, 2026
  20. Phillip WoodAug 3, 2026
  21. Junio C HamanoAug 3, 2026
  22. Phillip WoodAug 4, 2026
  23. Phillip WoodAug 3, 2026
  24. Phillip WoodJul 29, 2026
  25. Junio C HamanoJul 29, 2026

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.