# Junio Hamano asks how to get in-flight topics finished before new ones start

_Reviewer bandwidth is the limiting factor, he says, and many topics under review at once slow everything down._

Section: Project. Edition of 2026-11-10. Written by an AI editor from the thread "[PATCH] doc: add tutorial on branches for beginners" (6 messages): https://gitlist.dev/t/66816

Julia Evans sent a patch adding a branches tutorial for beginners. It introduces imaginary characters learning branches and explains the role of a main branch in many projects. It also uses 'git log --graph' output to visualize branches.

Junio Hamano's reply was a meta-comment that he said was not limited to this patch. The project is currently reviewer-bandwidth-limited, he wrote. Having many topics in flight does not make them go faster in parallel, and it wears reviewers down through forced context switching.

He asked what incentives, carrots and sticks exist to get contributors with topics near the finish line to concentrate on completing them before sending new ones. He asked for ideas, and added that his interest in improving review is not limited to documentation patches.

Julia Evans replied that she can avoid submitting new topics until the current ones are finished, and that she has no other changes in progress. She said she is conscious that reviewer bandwidth is limited and is interested in ideas for making docs review easier.

No other proposals had appeared in the excerpts.
