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, 21:56 UTC
Message-ID
<xmqqo6bxwtxa.fsf@gitster.g>
In-Reply-To
<pull.2307.git.1794259990263.gitgitgadget@gmail.com>
"Julia Evans via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 5 quoted lines
> From: Julia Evans <julia@jvns.ca>
>
> Because Git's branches are so flexible and the meaning of a branch is
> only what people assign to it, it's important to talk about some of the
> social context about branches. Do this in two ways:
A meta-comment, not limited to this patch.

We are currently reviewer-bandwidth-limited. Having many topics in-flight under review would not help these topics go any faster with greater parallelism. In fact, it slows everything down by wearing available reviewers down due to forced context switching.

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?
Previous: Julia Evans via GitGitGadgetNext: Julia Evans
Message 2 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.