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

Re: [PATCH] doc: add tutorial on branches for beginners

From
Julia Evans <julia@jvns.ca>
Date
Nov 10, 2026, 14:31 UTC
Message-ID
<75ad021c-b23b-49c8-818f-c28b57436aa3@app.fastmail.com>
In-Reply-To
<xmqqecctwt7x.fsf@gitster.g>
On Mon, Nov 9, 2026, at 5:11 PM, Junio C Hamano wrote:
Show 17 quoted lines
> "Julia Evans" <julia@jvns.ca> writes:
>
>>> I wonder what incentives, carrots and sticks we have on those who
>>> have in-flight topics that are so close to the finish line to
>>> concentrate on completing these topics before sending new ones.
>>>
>>> Ideas?
>>
>> For sure, I can avoid submitting new topics in the future until the
>> current ones are finished. I don't have any other changes in progress
>> in any case. 
>>
>> I'm very conscious that reviewer bandwidth is limited and I'm very
>> interested in ideas for how to make the docs review process easier.
>
> My interest in making review process better is not limited to
> documentation patches, though.

When I applied for funding from the Sovereign Tech Agency to work on the Git project's documentation, the main risk I flagged in my application was that reviewer capacity in the project is very limited. I tried to deal with this in a several ways:

1. I emailed a few people who had reviewed my patches in the past to ask
if they would be have capacity to do review on the new patches.
Patrick and Ben agreed to do some reviews which I really appreciate.
2. I applied for a relatively small amount of funding, which limits how
many hours Marie and I actually spent writing. Fewer hours spent writing
means less work to review :)
3. We recruited dozens of test readers to participate in a kind of side
review process. That doesn't serve the same function as the mailing list
review of course, but it hugely improves the final quality of the document
without introducing extra pressure on Git project's reviewers.

I don't know which of these strategies would apply to code changes but those are some of things I've tried so far.

Previous: Junio C HamanoNext: Julia Evans
Message 5 of 6 in “doc: add tutorial on branches for beginners”
  1. doc: add tutorial on branches for beginnersJulia Evans via GitGitGadget, Nov 9, 2026
  2. Junio C HamanoNov 9, 2026
  3. Julia EvansNov 9, 2026
  4. Junio C HamanoNov 9, 2026
  5. Julia EvansNov 10, 2026
  6. Julia EvansNov 18, 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.