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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 9, 2026, 22:11 UTC
Message-ID
<xmqqecctwt7x.fsf@gitster.g>
In-Reply-To
<4696f458-62b5-4d18-a74c-aa692708f7d0@app.fastmail.com>
"Julia Evans" <julia@jvns.ca> writes:
Show 12 quoted lines
>> 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.

Thanks.
Previous: Julia EvansNext: Julia Evans
Message 4 of 5 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

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.