From: Junio C Hamano <gitster@pobox.com>
To: "Julia Evans" <julia@jvns.ca>
Cc: "Julia Evans" <gitgitgadget@gmail.com>,
git@vger.kernel.org, "Patrick Steinhardt" <ps@pks.im>,
"D. Ben Knoble" <ben.knoble@gmail.com>
Subject: Re: [PATCH] doc: add tutorial on branches for beginners
Date: Mon, 09 Nov 2026 14:11:30 -0800 [thread overview]
Message-ID: <xmqqecctwt7x.fsf@gitster.g> (raw)
In-Reply-To: <4696f458-62b5-4d18-a74c-aa692708f7d0@app.fastmail.com> (Julia Evans's message of "Mon, 09 Nov 2026 17:01:01 -0500")
"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.
Thanks.
next prev parent reply other threads:[~2026-11-09 22:11 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
2026-11-09 22:01 ` Julia Evans
2026-11-09 22:11 ` Junio C Hamano [this message]
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=xmqqecctwt7x.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