From: Junio C Hamano <gitster@pobox.com>
To: "Julia Evans via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>,
"D. Ben Knoble" <ben.knoble@gmail.com>,
Julia Evans <julia@jvns.ca>
Subject: Re: [PATCH] doc: add tutorial on branches for beginners
Date: Mon, 09 Nov 2026 13:56:17 -0800 [thread overview]
Message-ID: <xmqqo6bxwtxa.fsf@gitster.g> (raw)
In-Reply-To: <pull.2307.git.1794259990263.gitgitgadget@gmail.com> (Julia Evans via GitGitGadget's message of "Mon, 09 Nov 2026 21:33:10 +0000")
"Julia Evans via GitGitGadget" <gitgitgadget@gmail.com> writes:
> 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?
next prev parent reply other threads:[~2026-11-09 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 21:33 [PATCH] doc: add tutorial on branches for beginners Julia Evans via GitGitGadget
2026-11-09 21:56 ` Junio C Hamano [this message]
2026-11-09 22:01 ` Julia Evans
2026-11-09 22:11 ` Junio C Hamano
2026-11-10 14:31 ` Julia Evans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqo6bxwtxa.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=julia@jvns.ca \
--cc=ps@pks.im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox