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?